open-index/open-npm huggingface dataset:
npm package: @mcdkio/n3m
Description: Deterministic password generator using PBKDF2-HMAC-SHA256
Author: mcotdev
Latest version: 1.0.0

# n3m

Deterministic password generator using PBKDF2-HMAC-SHA256.

## Installation

```bash
npm install -g n3m
```

## Usage

```bash
n3m <master_password> <item>
```

### Example

```bash
n3m "my-secret-master" gmail
# Output: a3hk5v2xpm9w
# (copied to clipboard)
```

## How It Works

1. Combines your master password with the item name using PBKDF2 (100,000 iterations)
2. Generates a deterministic 12-character password with digits and letters
3. Same inputs always produce the same password

## Features

- **Zero dependencies** - uses Node.js built-in crypto
- **Deterministic** - same master + item = same password
- **Secure** - PBKDF2-HMAC-SHA256 with 100k iterations
- **Clipboard** - automatically copies to clipboard (Linux with xclip)

## License

MIT
npm package: @mcdougald/eslint-config
Description: Personal ESLint configurations for Trevor McDougald's projects.
Author: Trevor McDougald
Latest version: 1.0.2

# @mcdougald/eslint-config

Personal ESLint configurations for Trevor McDougald's projects.

## Installation

```bash
npm i -D @mcdougald/eslint-config
```

Create an `eslint.config.ts` file with the following content:

```js
import { defineConfig } from '@mcdougald/eslint-config'

export default defineConfig({
  // Custom ESLint configuration options
})
```

### Options

```ts
type Options = {
  // Required
  // The root directory of the TypeScript configuration
  tsconfigRootDir: string
  // Optional
  // Enable React specific linting rules
  react?: boolean
  // Optional
  // Enable Next.js specific linting rules
  nextjs?: boolean
  // Optional
  // Specify the entry point for Tailwind CSS (also enable ESLint rules for tailwindcss)
  tailwindEntryPoint?: string
  // Optional
  // Specify glob patterns for Vitest (also enable ESLint rules for vitest)
  vitestGlob?: string
  // Optional
  // Specify glob patterns for Playwright (also enable ESLint rules for playwright)
  playwrightGlob?: string
  // Optional
  // Specify files to ignore
  ignores?: string[]
}
```
npm package: @mcdougald/prettier-config
Description: Personal Prettier configurations for Nelson Lai projects.
Author: Trevor McDougald
Latest version: 0.1.0

# @mcdougald/prettier-config

Personal Prettier configurations for Nelson Lai projects.

## Installation

```bash
npm i -D @mcdougald/prettier-config prettier-plugin-packagejson
```

Create a `prettier.config.js` file with the following content:

```js
import { defineConfig } from '@mcdougald/prettier-config'

export default defineConfig({
  // Custom Prettier configuration options
})
```
npm package: @mcdougald/typescript-config
Description: Personal TypeScript configurations for Nelson Lai projects.
Author: Trevor McDougald
Latest version: 0.0.3

# @mcdougald/typescript-config

Personal TypeScript configurations for Nelson Lai projects.

## Installation

```bash
npm i -D @mcdougald/typescript-config
```

Create a `tsconfig.json` file with the following content:

```jsonc
{
  "extends": "@mcdougald/typescript-config/base.json",
  "compilerOptions": {
    // Custom TypeScript configuration options
  }
}
```

### Presets

You can also use predefined presets for your configuration.

- `@mcdougald/typescript-config/base.json`
- `@mcdougald/typescript-config/next.json`
- `@mcdougald/typescript-config/react-library.json`
npm package: @mcduckswap/sdk
Description: 🛠 An SDK for building applications on top of Pancakeswap.
Latest version: 1.0.0

# Pancakeswap SDK

Forked from the [Uniswap SDK](https://github.com/Uniswap/uniswap-v2-sdk/commit/a88048e9c4198a5bdaea00883ca00c8c8e582605).

You can refer to the Uniswap SDK documentation [uniswap.org](https://uniswap.org/docs/v2/SDK/getting-started/).

## Running tests

To run the tests, follow these steps. You must have at least node v10 and [yarn](https://yarnpkg.com/) installed.

First clone the repository:

```sh
git clone https://github.com/pancakeswap/pancake-swap-sdk.git
```

Move into the pancakeswap-sdk working directory

```sh
cd pancakeswap-sdk/
```

Install dependencies

```sh
yarn install
```

Run tests

```sh
yarn test
```

You should see output like the following:

```sh
yarn run v1.22.4
$ tsdx test
 PASS  test/constants.test.ts
 PASS  test/pair.test.ts
 PASS  test/fraction.test.ts
 PASS  test/miscellaneous.test.ts
 PASS  test/entities.test.ts
 PASS  test/trade.test.ts

Test Suites: 1 skipped, 6 passed, 6 of 7 total
Tests:       3 skipped, 82 passed, 85 total
Snapshots:   0 total
Time:        5.091s
Ran all test suites.
✨  Done in 6.61s.
```
npm package: @mcduckswap/uikit
Description: Set of UI components for pancake projects
Latest version: 1.0.6

# 🥞 Pancake UIkit

[![Version](https://img.shields.io/npm/v/@pancakeswap-libs/uikit)](https://www.npmjs.com/package/@pancakeswap-libs/uikit) [![Size](https://img.shields.io/bundlephobia/min/@pancakeswap-libs/uikit)](https://www.npmjs.com/package/@pancakeswap-libs/uikit)

Pancake UIkit is a set of React components and hooks used to build pages on Pancake's apps. It also contains a theme file for dark and light mode.

## Install

`yarn add @pancakeswap-libs/uikit`

## Setup

### Theme

Before using Pancake UIkit, you need to provide the theme file to styled-component.

```
import { ThemeProvider } from 'styled-components'
import { light, dark } from '@pancakeswap-libs/uikit'
...
<ThemeProvider theme={isDark}>...</ThemeProvider>
```

### Reset

A reset CSS is available as a global styled component.

```
import { ResetCSS } from '@pancakeswap-libs/uikit'
...
<ResetCSS />
```

### Types

This project is built with Typescript and export all the relevant types.

## How to use the UIkit

If you want to use components from the UIkit, check the [Storybook documentation](https://pancakeswap.github.io/pancake-uikit/)
npm package: @mceachen/salita
Description: Automatically upgrade all dependencies, devDependencies, and peerDependencies
Author: Tim Branyen
Latest version: 0.11.1
Deprecated: Obsolete. Use the current "salita" package instead.

# Salita

**This fork applies PR [18](https://github.com/tbranyen/salita/pull/18) and
[19](https://github.com/tbranyen/salita/pull/19).**

Automatically upgrade all dependencies and devDependencies to their latest
stable semver.

## Install

```bash
npm install salita -g
```

## Usage

```bash
# Change into directory with package.json.
cd my_project

# Upgrade all dependencies.
salita
```

## Options

* `--no-color`: prevents colorized output
* `--json`: provides parseable JSON output (also disables colors)
* `--dry-run` / `-n`: prevents changes to `package.json`
* `--ignore-stars`: ignore updates to packages that are set to "\*"
* `--ignore-pegged`: ignore updates to packages that are pegged to a single
  version, rather than a range
* `--check`: implies "dry-run"; and returns with an exit code matching the
  number of updated dependencies.

## Example

You can see in the example below that dependencies are always resolved to their
latest stable, instead of just the latest version tagged:

![Terminal](http://tbranyen.com/u/7bc20890.png)
npm package: @mcelestino-conversion/a11y-widget
Description: Accessibility Widget - WCAG 2.1 AA-aligned support layer
Latest version: 1.1.0

# Accessibility Widget

WCAG 2.1 AA-aligned accessibility widget support layer.

## Installation

```bash
npm install @careerdriver-ai/a11y-widget
```

## Usage

### NPM (ES Modules)

```javascript
import { initA11yWidget } from "@careerdriver-ai/a11y-widget";
import "@careerdriver-ai/a11y-widget/styles.css";

initA11yWidget({ 
  siteId: "example.com",
  position: "right"
});
```

### CDN (Traditional)

```html
<script>
  window.__A11Y_WIDGET__ = {
    siteId: "example.com",
    position: "right"
  };
</script>
<script src="https://cdn.jsdelivr.net/gh/braieswabe/A11-Widget@v1.1.0/a11y-widget-loader-v1.1.0.js" defer></script>
```

## Configuration

Both methods support the same configuration options:

- `siteId`: Site identifier (auto-detected from hostname if not provided)
- `position`: Widget position - `"left"` or `"right"` (default: `"right"`)
- `surfaces`: CSS selectors for surfaces (default: `["body"]`)
- `globalMode`: Apply transformations to entire website (default: `false`)
- `keyboardShortcut`: Keyboard shortcut - `"Alt+A"`, `"Ctrl+Alt+A"`, or `null` to disable (default: `"Alt+A"`)
- `initialOpen`: Open widget on page load (default: `false`)
- `zIndex`: Widget z-index (default: `2147483000`)
- `features`: Feature flags object (all enabled by default)

See full documentation for complete configuration options.

## Browser Support

Modern browsers with ES module support.

## License

MIT
npm package: @mcell/mcell-mcp-server
Description: A stdio MCP server with image processing and S3 upload tools.
Author: mcell
Latest version: 0.1.2

# mcell-mcp-server

`mcell-mcp-server` 是一个基于 `stdio` 的 MCP Server，定位为 mcell 常用工具合集。当前内置：

1. 图片处理：压缩（可选 resize）、格式转换
2. S3 对象存储上传

## 工具列表

### 1) `image_compress`

压缩图片，可选调整尺寸。

- `input_path` (string, required): 源图片路径
- `output_path` (string, optional): 输出路径
- `quality` (1-100, optional, default: 80): 压缩质量
- `format` (`jpeg|png|webp|avif|tiff|heif|gif`, optional): 输出格式
- `width` / `height` (int, optional): resize 尺寸
- `fit` (`cover|contain|fill|inside|outside`, optional): resize 策略

### 2) `image_convert`

图片格式转换。

- `input_path` (string, required): 源图片路径
- `output_format` (`jpeg|png|webp|avif|tiff|heif|gif`, required): 目标格式
- `output_path` (string, optional): 输出路径
- `quality` (1-100, optional, default: 85): 编码质量

### 3) `s3_upload`

上传本地文件到 S3 或兼容 S3 的对象存储。

- `file_path` (string, required): 本地文件路径
- `bucket` (string, required): 桶名
- `key` (string, required): 对象 key
- `region` (string, optional): 默认 `AWS_REGION` 或 `us-east-1`
- `endpoint` (url, optional): S3 兼容存储 endpoint（如 MinIO/R2）
- `force_path_style` (boolean, optional): 是否使用 path-style
- `content_type` (string, optional): 显式 Content-Type
- `metadata` (record<string,string>, optional): 对象元数据

## 本地开发

```bash
npm install
npm run check
npm test
npm run build
npm start
```

`npm start` 后服务监听 `stdio`，供 MCP Client 拉起。

说明：

- `npm run build` 会先 `tsc`，再对 `dist/**/*.js` 全量做压缩与丑化（`terser --compress --mangle`）。
- `npm run ci` 会执行 `check + coverage + build`，与 CI 保持一致。

## 用户安装与运行（推荐）

发布 npm 后，用户可直接：

```bash
npx -y @mcell/mcell-mcp-server
```

## MCP 集成示例

不同 agent 的配置文件格式不同，但核心都是配置 `command + args`。

### Codex（TOML 示例）

```toml
[mcp_servers.mcell]
command = "npx"
args = ["-y", "@mcell/mcell-mcp-server"]

[mcp_servers.mcell.env]
AWS_REGION = "us-east-1"
```

### Claude 系（JSON 片段示例）

```json
{
  "mcpServers": {
    "mcell": {
      "command": "npx",
      "args": ["-y", "@mcell/mcell-mcp-server"],
      "env": {
        "AWS_REGION": "us-east-1"
      }
    }
  }
}
```

### memo code / 其他 agent

填写同样的进程启动参数即可：

- `command`: `npx`
- `args`: `["-y", "@mcell/mcell-mcp-server"]`

## S3 凭证

使用 AWS SDK 默认凭证链，建议通过环境变量注入：

- `AWS_ACCESS_KEY_ID`
- `AWS_SECRET_ACCESS_KEY`
- `AWS_SESSION_TOKEN`（可选）
- `AWS_REGION`（可选）

## 发布建议

### 手动发布

1. 更新 `package.json` 的 `version`
2. 确认 `bin` 指向 `dist/index.js`
3. `npm run ci`
4. `npm publish --access public --provenance`

### 自动发布（GitHub Actions）

仓库包含两个 workflow：

- `.github/workflows/ci.yml`
  - `push/pull_request` 触发
  - 运行 `npm ci`、`npm run check`、`npm run test:coverage`、`npm run build`
- `.github/workflows/publish.yml`
  - `main` 分支 `package.json` 变化时触发
  - 只有当 `version` 与上一个 commit 不同时才会发布
  - 若 npm 上已存在该版本则跳过发布

需要在 GitHub 仓库 Secrets 中配置：

- `NPM_TOKEN`: npm publish token

发布后用户端基本只需 `npx -y @mcell/mcell-mcp-server` 即可接入。
npm package: @mcell/stack-mcp
Description: MCP server for multi-resource static datasets
Latest version: 0.2.1

# @mcell/stack-mcp

A local MCP server that reads multi-resource static datasets (blog posts, topics, topic articles, site pages, profile).

## Usage

```bash
npx -y @mcell/stack-mcp
```

By default it reads index data from:

`https://stack.mcell.top/mcp/index.json`

## Configure in MCP clients (example)

```json
{
  "mcpServers": {
    "cellstack": {
      "command": "npx",
      "args": ["-y", "@mcell/stack-mcp"]
    }
  }
}
```

The defaults are already built in:

- `STACK_MCP_INDEX_URL=https://stack.mcell.top/mcp/index.json`
- `STACK_MCP_CACHE_DIR=~/.cache/stack-mcp`

## Tools

- `read_last`: Latest content entries (`blog` + `topic_article` by default).
- `read_latest`: Alias of `read_last`.
- `list_resources`: General list/search tool across all resource types.
- `list_topics`: Topic overview list.
- `read_resource`: Read one resource by `id` or `slug`.
- `read_site_info`: Read site intro and profile resources.
- `search_articles`: Compatibility alias for content search.
- `read_article`: Compatibility alias for `read_resource`.
- `refresh_index`: Force refresh remote index cache.

## Environment Variables

- `STACK_MCP_INDEX_URL`: Static index JSON URL.
- `STACK_MCP_CACHE_DIR`: Local cache directory. Default: `~/.cache/stack-mcp`.
- `STACK_MCP_CACHE_TTL_SECONDS`: Cache TTL (seconds). Default: `1800`.
- `STACK_MCP_REQUEST_TIMEOUT_SECONDS`: HTTP timeout (seconds). Default: `20`.
- `STACK_MCP_DEBUG`: Optional debug log switch (`1`/`true`/`yes` to enable).

## Static Data Format

`index.json`:

```json
{
  "version": 2,
  "generatedAt": "2026-02-10T00:00:00.000Z",
  "stats": {
    "blog": 10,
    "topic": 3,
    "topic_article": 30,
    "site_page": 1,
    "profile": 1
  },
  "entries": [
    {
      "id": "blog:2026/example",
      "type": "blog",
      "slug": "2026/example",
      "title": "Example",
      "description": "Example summary",
      "url": "/blog/2026/example",
      "document": "articles/blog_2026_example.json",
      "extra": {
        "section": "blog",
        "contentFormat": "markdown"
      }
    }
  ]
}
```

Document JSON:

```json
{
  "id": "blog:2026/example",
  "type": "blog",
  "slug": "2026/example",
  "title": "Example",
  "url": "/blog/2026/example",
  "document": "articles/blog_2026_example.json",
  "sourcePath": "content/blog/2026/example.md",
  "metadata": {},
  "content": "markdown body",
  "extra": {}
}
```

Other generated files:

- `latest.json`: precomputed latest content entries.
- `catalog.json`: ids grouped by type plus `contentIds`.

## Build Data in This Repository

The site repository generates static data during build:

```bash
pnpm run mcp:build-data
```

Generated files are written to `public/mcp/`.
npm package: @mcesarczyk/react-components
Description: React components library
Author: Michał Cesarczyk
Latest version: 1.3.2

# React-components

## 1. Atoms

### 1.1. Button

Usage:

```jsx
import { Button } from "@mcesarczyk/react-components";

<Button
  buttonType={
    "primary" | "secondary" | "warning" | "error" | "outlined" | "disabled"
  }
  size={"default" | "small" | "large" | "xxl"}
  rounded={"default" | "sm" | "lg" | "xl" | "xxl" | "full" | "none"}
  spacing={"default" | "small" | "large" | "xxl"}
  label={String}
  leftIcon={ReactNode}
  rightIcon={ReactNode}
  onClick={MouseEventHandler<HTMLButtonElement>}
/>;
```

Besides the options, the Button component accepts all the props from the native button element.

### 1.2. Select

Usage:

```jsx
import { Select } from '@mcesarczyk/react-components';

<Select
  options={Array<{ value: string | number, label: string }>}
/>
```

Besides the options, the Select component accepts all the props from the native select element.
npm package: @mcesarczyk/react-hooks
Description: react hooks used in my projects
Author: Michał Cesarczyk
Latest version: 1.0.3

# React-hooks

### 1. useOnClickOutside
Runs a callback when a click event is detected outside of the provided element.

Usage:
```javascript
export const Wrapper = () => {
const elementRef = useRef<HTMLDivElement>(null);
  ...

  useOnClickOutside(elementRef, doSomething);

  return (
      <div ref={elementRef} />
  );
};
```
npm package: @mcf/redux-account-middleware
Description: redux middleware for account
Author: MCF Team
Latest version: 0.1.1

redux-account-middleware
============================
This library helps with the helps with the management of authentication account lifecycle

https://www.npmjs.com/package/@mcf/redux-account-middleware

# Installation

```bash
npm i @mcf/redux-account-middleware --save
```
or
```bash
yarn add @mcf/redux-account-middleware
```

# Usage

To run the middleware, we'll have to connect it to the Redux Store.

#### `main.js`

```javascript
import {createStore, applyMiddleware, combineReducers} from 'redux'
import {
  accountReducer,
  createAccountMiddleware,
} from './middleware/account';

// create the account middleware
const accountMiddleware = createAccountMiddleware({
  fetchAccountRequest: fetch('getAccountRequest'),
  logoutRequest: fetch('logoutRequest'),
  refreshTokenRequest: fetch('refreshTokenRequest'),
});

import reducer from './reducers'

const sagaMiddleware = createSagaMiddleware()
// mount it on the Store
const store = createStore(
  // include the account reducer into the main reducer
  combineReducers({
    account: accountReducer,
    ...reducer,
  }),
  applyMiddleware(accountMiddleware)
)

// render the application
```

# Refresh token

This redux middleware will try to refresh the token by calling refresh token api if there is any dispatched action to the redux (given that user is logged in and token expiring within refreshIntervalMinutes)

there are exceptions where the middleware is in the middle of requesting new token and getting account info, or user is logging out  
which represented by status below

- `REFRESH_REQUESTED`: When refresh is already requested and in progress. This is to prevent duplicates refresh request.
- `REFRESH_RECEIVED`: This is the intermediate state where account api will be called in next action. This is to prevent duplicates refresh request.
- `ACCOUNT_REQUESTED`: This is the intermediate state to get the latest token expiry from account api. This is to prevent duplicates refresh request.
- `LOGOUT_REQUESTED`: When there is a logout request on-going, We should stop refreshing the token. This is so that the user session will not be re-populated with the fresh token and log the user back in

so when the state is either any one mentioned above, refresh token api will not be called
npm package: @mcf/tracer
Description: Creates and exposes a Zipkin tracer for consumption by an Express-based application.
Latest version: 0.0.22

[![npm version](https://badge.fury.io/js/%40mcf%2Ftracer.svg)](https://badge.fury.io/js/%40mcf%2Ftracer)

# `@mcf/tracer`
Creates a Zipkin tracer for consumption by an Express-based application.

## Scope

- [x] Create a tracer

## Installation

```bash
npm i @mcf/tracer;
# OR
yarn add @mcf/tracer;
```

## Usage

```js
const {createTracer} = require('@mcf/tracer');
// OR
import {createTracer} from '@mcf/tracer';
```

### Basic

```js
import express from 'express';
import {expressMiddleware} from 'zipkin-instrumentation-express';
import {createTracer} from '@mcf/tracer';
const tracer = createTracer();
const server = express();
server.use(expressMiddleware({tracer}));
server.listen();

// access context from anywhere
import {MCF_TRACE_NAMESPACE} from '@mcf/tracer';
import {getNamespace} from 'cls-hooked';
const namespace = getNamespace(MCF_TRACE_NAMESPACE);
// do whatever you want with namespace

```

### Full Configuration (with defaults)

```js
import express from 'express';
import {expressMiddleware} from 'zipkin-instrumentation-express';
import {createTracer} from '@mcf/tracer';
const tracer = createTracer({
  httpHeaders: {},
  localServiceName: 'unknown',
  sampleRate: 0.5,
  syncIntervalMs: 1000,
  serverHost: 'localhost',
  serverPort: '9411',
  serverProtocol: 'http',
});
const server = express();
server.use(expressMiddleware({tracer}));
```

## API

### `.createTracer(:options)`
Creates the tracer instance. The `:options` parameter has the following schema:

| Key | Defaults To | Description | Environment variable
| --- | --- | --- | ---
| `httpHeaders` | `{}` | Additional HTTP headers to be sent to the Zipkin server | -
| `localServiceName` | `os.hostname() OR 'unknown'` | The identity of the current service | process.env.HOSTNAME
| `sampleRate` | `0.5` | The frequency of sampling by Zipkin. Settings this to 1.0 may cause your data store behind Zipkin to be populated very quickly. Use higher numbers for testing only | -
| `syncIntervalMs` | `1000` | Synchronises the data every X milliseconds | -
| `serverHost` | `"localhost"` | The hostname of your Zipkin service | process.env.ZIPKIN_HOST
| `serverPort` | `"9411"` | The port on which the Zipkin service is listening to | process.env.ZIPKIN_PORT
| `serverProtocol` | `"http"` | The string identifier of the protocol your are using. Typically `"http"` or `"https"` | process.env.ZIPKIN_PROTOCOL

## Changelog
### 0.0.11
- Use cls-hooked for context implementation
### 0.0.6
- Added static exports for retrieving a Winston formatter to add context details to the logs
- Release!
### 0.0.5
- Added static exports for retrieving the context provider middleware
- Added static exports for retrieving the Morgan tokenizers
### 0.0.4
- Added Morgan tokenizer generator
### 0.0.3
- Initial release
npm package: @mcfagentic/agenttools
Description: x402 client for MCF Agentic gateway — 187 AI agent tool endpoints (CRM, Email, Scheduling, Marketing, Ads, UGC, Pipeline, and more). Pay-per-request with USDC on Base.
Author: Cameron Fagan
Latest version: 1.0.0

# agenttools

x402 client for the MCF Agentic gateway. 187 pay-per-request AI agent tool endpoints.

Payments in USDC on Base L2 via the [x402 protocol](https://x402.org).

## Install

```bash
npm install agenttools
```

## Quick Start

```typescript
import { AgentTools } from "agenttools";

const tools = new AgentTools("https://gateway.mcfagentic.com");

// Generate leads with the full AI pipeline ($1.00/call)
const leads = await tools.pipeline.generateLeads({
  industry: "plumbing",
  location: "Dallas, TX",
  count: 3,
  include_outreach: true,
});

// CRM operations ($0.001-$0.05/call)
const accounts = await tools.crm.listAccounts();
await tools.crm.createLead({ name: "Acme Corp", email: "info@acme.com" });

// AI email classification ($0.05/call)
const result = await tools.email.classify({
  subject: "Re: Your proposal",
  body: "Looks great, let's schedule a call.",
});

// Send email ($0.05/call)
await tools.email.send({
  to: "client@example.com",
  subject: "Follow-up",
  html: "<p>Thanks for your interest!</p>",
});
```

## Tools

| Tool | Endpoints | Price Range | Description |
|------|-----------|-------------|-------------|
| **Pipeline** | 3 | $0.25-$1.00 | Autonomous lead gen — one call, full research + outreach |
| **CRM** | 21 | $0.001-$0.05 | Accounts, leads, deals, contacts, pipelines, work orders |
| **Email** | 13 | $0.001-$0.10 | Send, classify, AI reply, entity extraction |
| **Scheduling** | 9 | $0.001-$0.01 | Staff, appointments, availability, events |
| **Marketing** | 11 | $0.001-$0.05 | Prospects, campaigns, outreach, solutions |
| **Ads** | 23 | $0.001-$0.10 | Campaigns, A/B tests, audits, AI optimization |
| **UGC** | 32 | $0.001-$0.25 | AI video pipeline, TikTok, YouTube, media library |
| **Accounting** | 16 | $0.001-$0.10 | Invoices, expenses, job costs, P&L reports |
| **Analytics** | 15 | $0.001-$0.05 | Events, funnels, cohorts, attribution, revenue |
| **Notifications** | 4 | $0.001-$0.05 | Templates, send (email/SMS), delivery log |
| **Consulting** | 31 | $0.001-$0.25 | AI proposals, client mgmt, transcription, scoring |

## Payment

All endpoints use x402 (HTTP 402). Send a request without payment to get pricing info:

```typescript
try {
  await tools.pipeline.generateLeads({ industry: "hvac", location: "Austin, TX" });
} catch (err) {
  if (err.name === "X402PaymentRequired") {
    console.log(err.pricing); // { price: "$1.00", network: "eip155:8453", ... }
  }
}
```

For automatic payments, use an x402-compatible HTTP client like `@x402/fetch`.

## Gateway

Default: `https://gateway.mcfagentic.com`

GitHub: [Cameron48/agenttools](https://github.com/Cameron48/agenttools)

## License

MIT
npm package: @mcfarljw/capacitor-audio
Description: A native audio plugin for Ionic Capacitor.
Author: Joshua McFarland
Latest version: 2.0.1

# @mcfarljw/capacitor-audio

A native audio plugin for Ionic Capacitor.

## Install

```bash
npm install @mcfarljw/capacitor-audio
npx cap sync
```

## API

<docgen-index>

* [`play(...)`](#play)
* [`stop(...)`](#stop)
* [`stopAll()`](#stopall)

</docgen-index>

<docgen-api>
<!--Update the source file JSDoc comments and rerun docgen to update the docs below-->

### play(...)

```typescript
play(options: { path: string; track: number; }) => Promise<void>
```

| Param         | Type                                          |
| ------------- | --------------------------------------------- |
| **`options`** | <code>{ path: string; track: number; }</code> |

--------------------


### stop(...)

```typescript
stop(options: { track: number; }) => Promise<void>
```

| Param         | Type                            |
| ------------- | ------------------------------- |
| **`options`** | <code>{ track: number; }</code> |

--------------------


### stopAll()

```typescript
stopAll() => Promise<void>
```

--------------------

</docgen-api>
npm package: @mcfarljw/capawesome-cloud
Description: A typed API client for the Capawesome Cloud
Latest version: 0.1.1

# @mcfarljw/capawesome-cloud

<!-- automd:badges color=yellow -->

[![npm version](https://img.shields.io/npm/v/@mcfarljw/capawesome-cloud?color=yellow)](https://npmjs.com/package/@mcfarljw/capawesome-cloud)
[![npm downloads](https://img.shields.io/npm/dm/@mcfarljw/capawesome-cloud?color=yellow)](https://npm.chart.dev/@mcfarljw/capawesome-cloud)

<!-- /automd -->

## Usage

Install the package:

```sh
npx nypm install @mcfarljw/capawesome-cloud

```

Create a client:

```ts
import { createCapawesomeClient } from "@mcfarljw/capawesome-cloud";

const client = createCapawesomeClient({
  token: process.env.CAPAWESOME_TOKEN,
});
```

Call endpoints with typed `path`, `query`, and `body` options inferred from the
OpenAPI-generated types in `src/types/capawesome.ts`:

```ts
const apps = await client.get("/v1/apps", {
  query: { limit: "20" },
});

await client.post("/v1/apps/{appId}/channels", {
  path: { appId: "app_123" },
  body: { name: "production" },
});
```

Responses currently default to `unknown` because the generated OpenAPI operation
types expose `responses: never`. You can provide a response type when you call
the client:

```ts
const app = await client.get<{ data: { id: string; name: string } }>("/v1/apps/{appId}", {
  path: { appId: "app_123" },
});
```

You can also use the generic `request` method if you prefer passing an explicit
HTTP method:

```ts
const builds = await client.request("get", "/v1/apps/{appId}/builds", {
  path: { appId: "app_123" },
  query: { limit: "10" },
});
```

## Development

<details>

<summary>local development</summary>

- Clone this repository
- Install latest LTS version of [Node.js](https://nodejs.org/en/)
- Enable [Corepack](https://github.com/nodejs/corepack) using `corepack enable`
- Install dependencies using `pnpm install`
- Run interactive tests using `pnpm dev`

</details>

## License

Published under the [MIT](https://github.com/mcfarljw/capawesome-cloud/blob/main/LICENSE) license 💛.
npm package: @mcfarljw/nuxt-vuetify
Description: Nuxt 3 module for Vuetify 3
Latest version: 3.0.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @mcfarljw/nuxt-vuetify

[![npm version][npm-version-src]][npm-version-href]
[![npm downloads][npm-downloads-src]][npm-downloads-href]
[![License][license-src]][license-href]
[![Nuxt][nuxt-src]][nuxt-href]

My new Nuxt module for doing amazing things.

- [✨ &nbsp;Release Notes](/CHANGELOG.md)
<!-- - [🏀 Online playground](https://stackblitz.com/github/your-org/my-module?file=playground%2Fapp.vue) -->
<!-- - [📖 &nbsp;Documentation](https://example.com) -->

## Features

<!-- Highlight some of the features your module provide here -->
- ⛰ &nbsp;Foo
- 🚠 &nbsp;Bar
- 🌲 &nbsp;Baz

## Quick Setup

1. Add `my-module` dependency to your project

```bash
# Using pnpm
pnpm add -D my-module

# Using yarn
yarn add --dev my-module

# Using npm
npm install --save-dev my-module
```

2. Add `my-module` to the `modules` section of `nuxt.config.ts`

```js
export default defineNuxtConfig({
  modules: [
    'my-module'
  ]
})
```

That's it! You can now use @mcfarljw/nuxt-vuetify in your Nuxt app ✨

## Development

```bash
# Install dependencies
npm install

# Generate type stubs
npm run dev:prepare

# Develop with the playground
npm run dev

# Build the playground
npm run dev:build

# Run ESLint
npm run lint

# Run Vitest
npm run test
npm run test:watch

# Release new version
npm run release
```

<!-- Badges -->
[npm-version-src]: https://img.shields.io/npm/v/my-module/latest.svg?style=flat&colorA=18181B&colorB=28CF8D
[npm-version-href]: https://npmjs.com/package/my-module

[npm-downloads-src]: https://img.shields.io/npm/dm/my-module.svg?style=flat&colorA=18181B&colorB=28CF8D
[npm-downloads-href]: https://npmjs.com/package/my-module

[license-src]: https://img.shields.io/npm/l/my-module.svg?style=flat&colorA=18181B&colorB=28CF8D
[license-href]: https://npmjs.com/package/my-module

[nuxt-src]: https://img.shields.io/badge/Nuxt-18181B?logo=nuxt.js
[nuxt-href]: https://nuxt.com