Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ForgeyClap/claude-forgenpx agentmods add skills/forgeyclap/claude-forge/forge-qualityWrote 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-quality)<a href="https://agentmods.dev/skills/forgeyclap/claude-forge/forge-quality"><img src="https://agentmods.dev/badge/skills/forgeyclap/claude-forge/forge-quality/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/skills/forgeyclap/claude-forge/forge-quality"><img src="https://agentmods.dev/badge/skills/forgeyclap/claude-forge/forge-quality.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.00040 | $0.00636 |
| Opus 5.5 | $0.00016 | $0.00254 |
| Sonnet 5.5 | $0.00008 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
forge-quality 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 19d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
forge-quality — Quality Intelligence Layer
Layer-2 instruction (progressive disclosure): this file is small; domain knowledge lives in layer 3
(.claude/config/quality/cards/*.md, 0 tokens until loaded). The module is
.claude/forge-bin/forge-quality.cjs; the canonical domain list is
.claude/config/orchestration/domain-catalog.json — on a conflict the CATALOG wins and the
diverging seam gets fixed, never a second list started.
Commands
node .claude/forge-bin/forge-quality.cjs analyze "<the mission>" # THE entry point: profile + playbook + lenses + omissions + card descriptors + council in one JSON (F-14)
node .claude/forge-bin/forge-quality.cjs profile "<the mission>" # the MissionProfile only
node .claude/forge-bin/forge-quality.cjs card <slug> # one knowledge card (layer 3, on-demand)
node .claude/forge-bin/forge-quality.cjs drift # catalog vs 4 seams — every difference is a finding (exit 3 on drift)
node .claude/forge-bin/forge-quality.cjs kernel # the fixed Quality Kernel (~600-800 tokens)
Workflow (router Step 1 — required for BUILD tasks)
- Run
analyze; machine output beats any human-written table.classification_confidence: nonemeans: the fallback is an ASSUMPTION — resolve the type explicitly (intake) before building. - Lenses: every lens gets EXACTLY one disposition (RELEVANT/NOT_APPLICABLE/DEFERRED/OWNER_GATED) with a reason. Silently skipping does not exist; neither does silently adding one.
- Omissions are candidate requirements (pre-validated;
omissions_validmust be true — a hand-edited card goes back throughvalidateRequirementCard). A RESEARCH_HYPOTHESIS never becomes a hard requirement directly — promotion requiresconfirmed_by{type: local-validation| official-source|experiment, ref}. - Knowledge cards: load only descriptors with
exists: trueviacard <slug>— max 6 cards, max 3 retrieval rounds. A missing card is an honest notice, never invented content.
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.
- 19d ago Changed · -5 tokens per session ec55d003b7a7
- 22d ago First seen · 44 lines · 45 tokens per session scan A 9c6b272d8c41
forge-quality is a skill published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 16d ago), licensed MIT. It adds 40 tokens to every session and 636 once invoked, about $0.0002 per session on Opus 5.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-09-24.
Other skills, from other repositories
returns-policy
Answer return, refund, and warranty questions for electronics. Use when the user mentions returns, refunds, RMAs, warranty coverage, damaged items, or opened packaging.
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
contribute-spec-fix
Fix a broken OpenAPI spec in jentic-public-apis with an OpenAPI Overlay, validate it (spectral lint + idempotency check), and contribute it back via a PR to the community catalog. Falls back to applying the same overlay to the local Jentic registry if the user can't wait for maintainer approval, and closes the loop by…
jentic
Calls third-party APIs through a Jentic One instance — governed, credential-managed access where the agent searches for an operation, inspects it, and executes it through an audited broker that holds the credentials (identity → discover → check access → execute). Applies when the user asks to call an external API or…
review
Use when operating as the Fabrik Review stage agent. This skill guides code review of an implementation, finding and fixing issues, and ensuring the PR is ready for human review.
implement-comment
Use when operating as the Fabrik Implement comment reviewer. This skill guides applying user-requested code changes during implementation, committing and pushing, and updating the task checklist — without signaling stage completion.