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 skills add chrono-meta/forge-harness --skill phantom-quenchgit clone --depth 1 https://github.com/chrono-meta/forge-harnessWrote 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/chrono-meta/forge-harness/phantom-quench)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/phantom-quench"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/phantom-quench.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 16 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00171 | $0.07273 |
| Opus 5 | $0.00086 | $0.03637 |
| Sonnet 5 | $0.00034 | $0.01455 |
| Haiku 4.5 | $0.00017 | $0.00727 |
Grade A, and why
phantom-quench 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 8d 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 — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
phantom-quench — Input Tracing Grounding Audit
Just because an artifact looks plausible doesn't mean it's grounded in source. plausible ≠ grounded.
Renamed from
source-grounding-audit(2026-06-06) — the grounding member of the quench series (steel-quench · phantom-quench · goal-quench). Same skill, same ruleset; only the label changed to fit the family. The v1 paper (Zenodo 10.5281/zenodo.20397566) cites the old name — that is the historical record, not a phantom (paper/forge_harness_v1.0.htmlis left unchanged by design; readers map source-grounding-audit (v1) = phantom-quench (current)). The deprecated redirect stub directory was removed 2026-06-12 — old-name utterances ("source grounding audit", "grounding audit") route here via this description's trigger phrases. This is a label rename, not a capability change — phantom-quench does not fuse steel-quench or inject faults; those remain separate (orthogonality is deliberate — see Role Separation below).Quench-series semantics (resolves the "quench what?" question): each member subjects a different thing to the forge — steel-quench hardens an existing output; phantom-quench hardens the system against mistaking the absent for present (the phantom illusion — not the phantom as a material to harden); goal-quench hardens the goal itself into an advanced version. Same verb, consistent grammar.
Not the same as
phantom-gate.phantom-gateis the productized standalone phantom detector — a PyPI package run against any repo from the shell.phantom-quenchis the in-harness skill — the same detection lineage as a method invoked inside a Claude session against a declared source set. Tool vs skill; different delivery, shared idea.
When AI generates artifacts without reading the source, those artifacts look like domain knowledge but are actually Phantom Claims coming from LLM weights. This skill back-traces each claim in the artifact to the declared source to explicitly mark Phantoms.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 447 lines · 171 tokens per session scan A 1470317320bf
phantom-quench is a skill published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed today), licensed MIT. It adds 171 tokens to every session and 7,273 once invoked, about $0.0009 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 skills, from other repositories
taiyi-change
A TaiyiForge workflow stage for writing a change proposal in CHANGE.md, with checks for scope, risks, success criteria, and related project documents.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
taiyi-requirement
A requirements-analysis process that turns a proposed change into a REQUIREMENT.md document. It records user needs, acceptance checks, terminology, triggers, and dependencies, with different levels of detail for different project sizes.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-compress
A workflow tool for shrinking large coding-agent conversations and work files into shorter context notes. It can also coordinate separate agents for parallel development and create handoff notes for continuing work in a new session.