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/srnichols/plan-forge/forge-quenchnpx skills add srnichols/plan-forge --skill forge-quenchgit clone --depth 1 https://github.com/srnichols/plan-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/srnichols/plan-forge/forge-quench)<a href="https://agentmods.dev/skills/srnichols/plan-forge/forge-quench"><img src="https://agentmods.dev/badge/skills/srnichols/plan-forge/forge-quench.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.00051 | $0.01832 |
| Opus 5 | $0.00026 | $0.00916 |
| Sonnet 5 | $0.00010 | $0.00366 |
| Haiku 4.5 | $0.00005 | $0.00183 |
Grade A, and why
forge-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 yesterday.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Quench — Code Simplification Skill
Named after the metallurgical quenching process — rapidly cooling hot metal simplifies its crystal structure and hardens it.
Trigger
"Simplify this code" / "Reduce complexity" / "Clean up before review" / "Quench this module" / "Code is too complex"
Steps
1. Measure Complexity
Identify the most complex methods in the target files. Use .NET-appropriate static analysis:
# Install dotnet-counters for runtime diagnostics (optional)
dotnet tool install -g dotnet-counters
# Count methods exceeding 50 lines
grep -rn "public\|private\|protected\|internal" <target> --include="*.cs" | head -30
# Check cyclomatic complexity via JetBrains dotnet-inspect if available
# dotnet-inspect <target> --severity=WARNING
# Manual analysis: identify deep nesting, long switch statements, excessive branching
grep -rn "if\|else\|switch\|case\|catch" <target> --include="*.cs" | wc -l
List the top 3–5 most complex methods by:
- Line count (methods >50 lines)
- Nesting depth (>3 levels of indentation)
- Branch count (>5 if/else/switch branches)
- Parameter count (>4 parameters)
If no methods exceed thresholds: Report "No simplification candidates found" and STOP with a PASS.
2. Understand First (Chesterton's Fence)
Before simplifying ANY code, document WHY the complexity exists.
For each candidate function:
- Read the git blame to find when and why it was written
- Check if comments explain the reasoning
- Look for edge cases the complexity handles (null checks, retry logic, fallback paths)
- Document your understanding in a brief note
| Function | Lines | Why Complex | Still Valid? | Action |
|----------|-------|-------------|-------------|--------|
| processOrder() | 87 | Handles 3 payment providers + retry | Yes — 3 providers still active | Simplify: extract per-provider strategies |
| validateInput() | 62 | Legacy regex for 5 country formats | Partially — 2 formats deprecated | Simplify: remove deprecated formats |
| buildReport() | 45 | Single function, low nesting | N/A — not complex enough | Skip |
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.
- yesterday First seen · 172 lines · 51 tokens per session scan A d209d014d49d
forge-quench is a skill published in the GitHub repository srnichols/plan-forge (5 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,832 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
ux-ui
Use this agent when you need to design, audit, migrate, rewire, or rewrite UX/UI.
go
Project Kickstart - PRD-First Orchestrator.
docs
Use this agent when you need to create comprehensive technical and user documentation for approved features, tests, or debugged issues.
analytics
/analytics - Agent Usage Analytics.
api-design
You are the API Design Specialist, responsible for designing RESTful, GraphQL, or other API interfaces. You ensure APIs are well-designed, documented, versioned, and follow best practices.
explain
/explain - Execution Explainer.