Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/forgeyclap/claude-forge/forge-integrationnpx skills add ForgeyClap/claude-forge --skill forge-integrationgit clone --depth 1 https://github.com/ForgeyClap/claude-forgeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/forgeyclap/claude-forge/forge-integration)<a href="https://agentmods.dev/skills/forgeyclap/claude-forge/forge-integration"><img src="https://agentmods.dev/badge/skills/forgeyclap/claude-forge/forge-integration.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00039 | $0.00860 |
| Opus 5 | $0.00019 | $0.00430 |
| Sonnet 5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
forge-integration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge playbook — Business automation / API integration
This is a secrets + auth domain — security-reviewer is a useful (optional) advisor here. If the runtime is n8n, defer to forge-n8n.
Hard rules
- Secrets in env +
.env.exampleplaceholders; never in code or logs. - Webhook auth / signature verification on every inbound webhook.
- Input validation on all external data; minimal OAuth scopes.
- Idempotent writes (no duplicate side effects on retry).
- Outreach drafted only / no auto-send / no bulk without explicit confirmation (shared with
forge-scraping). - Dedicated agent identity (2026-07-12, video-research verified): integrations that READ e-mail/CRM-data or SEND on the owner's behalf SHOULD run under a dedicated agent identity — own mailbox/account, own OAuth grant, own API key — never the owner's personal credentials. Scope-minimization bounds operations, not data: a readonly token on the owner's mailbox still exposes their entire correspondence to a prompt-injected agent; a dedicated identity gives blast-radius containment + one-step revocation + a clean audit trail. Tiered: required-by-default for e-mail-read + external-send combinations (lethal-trifecta shape), advisory for low-risk one-way notifications. Surface the extra-account setup cost as an owner decision at integration planning and record the identity choice in the integration notes.
Team (conditional)
Lead: architect; security-reviewer available as an optional advisor. Specialists: silent-failure-hunter (dropped webhooks/retries), python-reviewer / typescript-reviewer, database-reviewer.
Skills / commands / MCP
n8n-workflow-patterns (if n8n); Gmail / Calendar / CRM / Slack MCP tools via ToolSearch.
Fan-out & flow
L2 single integration; L3 multi-service flow. Parallel: independent integrations (Gmail ∥ Calendar ∥ CRM). Serial: auth → fetch → transform → write-back.
Domain gates
All credentials in env; webhook signature/auth verified; retries + dead-letter for failed calls; no secrets/PII in logs; rate limits respected; any user-facing send gated behind explicit confirmation.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 40 lines · 39 tokens per session scan A a622809478a0
forge-integration is a skill published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 860 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
consulting-analysis
Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial analysis, industry research, competitive intelligence, investment due diligence, or any consulting-grade analytical report. This…
goal-draft
Turn a fuzzy intention into a /goal objective the Goal verifier can actually judge - one outcome, numbered binary "Done when" checks that leave evidence in the transcript, guardrails, a budget, and a block protocol. Use when the user wants to set or define a goal, asks whether a goal is good enough, or says "keep…
eliza-cloud
Use when the task involves Eliza Cloud or elizaOS Cloud as a managed backend, app platform, deployment target, billing layer, or monetization surface. The catch-all skill for any user request about THEIR existing apps / containers / earnings / credits / api-keys / analytics / billing / payment requests / payouts …
build-monetized-app
Use when the task is building a new app on Eliza Cloud that earns money — chat apps, agent apps, MCP-backed tools, anything that calls the cloud's chat/messages/inference endpoints on behalf of users. Covers app registration, container deploy, markup configuration, affiliate header, app charge requests, x402 payment…
eliza
Use for spawned coding/task agents working on the Eliza app or asking what the running Eliza agent can do. Covers the repo CWD, default skill loading and overrides, child-to-parent USESKILL calls, parent runtime context APIs, plugin loading/building, Cloud app/payment/domain/media capabilities, and how workers can ask…
finance-report
Masthead + KPI + 收入/烧钱图 + P&L 表 + 重点 + 展望.