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 commands/ferroxlabs/ijfw/metricsgit clone --depth 1 https://github.com/FerroxLabs/ijfwWrote 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/ferroxlabs/ijfw/metrics)<a href="https://agentmods.dev/commands/ferroxlabs/ijfw/metrics"><img src="https://agentmods.dev/badge/commands/ferroxlabs/ijfw/metrics.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.00037 | $0.00256 |
| Opus 5 | $0.00018 | $0.00128 |
| Sonnet 5 | $0.00007 | $0.00051 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
ijfw-metrics 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.
What it actually says
Call the ijfw_metrics MCP tool with:
period:$1if provided (one oftoday,7d,30d,all), else7dmetric:$2if provided (one oftokens,cost,sessions,routing), elsetokens
Render the result inside a fenced code block -- no extra commentary, no headers. The tool returns positive-framed text even when no data is available yet.
Examples the user might invoke:
/ijfw-metrics-- last 7 days, tokens/ijfw-metrics 30d cost-- last 30 days, cost in USD/ijfw-metrics all sessions-- all-time session counts and handoff rate/ijfw-metrics today routing-- today's routing mix
Footer note (only if data appears): metrics reflect clean session-ends only -- crashes or force-quits skip the Stop hook and undercount tokens for that turn.
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 · 21 lines · 37 tokens per session scan A 2191f5d2ef3e
ijfw-metrics is a command published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 10d ago), licensed MIT. It adds 37 tokens to every session and 256 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-30.
Other commands, from other repositories
constitution
根据交互输入或已提供原则创建或更新项目章程，并确保相关模板保持同步。.
meta-theory-verify
Run the appropriate MetaKim verification path.
core-review
Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).
resolve-conflicts
Resolve merge conflicts on a GitHub PR by merging the base branch into the PR branch in an isolated git worktree, with JSON/markdown-aware conflict resolution.
ship-pr
Commit all changes to a new branch, push, and open a PR for review. The original branch stays clean.
implement
Execute implementation by processing atomic task files one at a time with Context Pinning (Atomic Traceability Model).