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.
git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDockWrote 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/commands/rapiercraftstudios/forgedock/analytics)<a href="https://agentmods.dev/commands/rapiercraftstudios/forgedock/analytics"><img src="https://agentmods.dev/badge/commands/rapiercraftstudios/forgedock/analytics/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rapiercraftstudios/forgedock/analytics"><img src="https://agentmods.dev/badge/commands/rapiercraftstudios/forgedock/analytics.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00075 | $0.11601 |
| Opus 5.5 | $0.00030 | $0.04640 |
| Sonnet 5.5 | $0.00015 | $0.02320 |
| Haiku 4.5 | $0.00007 | $0.01160 |
Grade A, and why
analytics scanned grade A with 2 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 11d 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.
Reads MCP configurationlowAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
Agents MUST read this file for API keys, tokens, and login creds. Do NOT grep SOPS, do NOT hardcode tokens, do NOT look in `.mcp.json`. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
token = requests.post(sa['token_uri'], data={'grant_type': 'urn:ietf:params:oauth:grant-type:jwt-bearer', 'assertion': signed}).json()['access_token'] The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 11d ago Changed · +2 lines 6dac58f1653a
- 1mo ago First seen · 863 lines · 75 tokens per session scan A 965f8fbcf319
analytics is a command published in the GitHub repository RapierCraftStudios/ForgeDock (119 stars, last pushed 4d ago), licensed AGPL-3.0. It adds 75 tokens to every session and 11,601 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 2 findings (reads mcp configuration, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
workflow-automate
Automate CI/CD pipelines, releases, and development workflows with GitHub Actions, pre-commit hooks, and infrastructure automation.
ops-vercel
Command "ops-vercel" from christopherlouet/claude-base, covering ops-vercel agent (pointer), context, delegate to the vendor toolkit and related agents.
ops-infra-code
Implements Infrastructure as Code (IaC) with Terraform, CloudFormation or Pulumi.
ops-serverless
Deployment of serverless applications (AWS Lambda, Vercel, Cloudflare Workers).
work-flow-release
Complete workflow to prepare and publish a release.
ops-ci
Configure CI/CD pipelines (GitHub Actions, GitLab CI, etc.).