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 victusfate/scaffold --skill prunegit clone --depth 1 https://github.com/victusfate/scaffoldWrote 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/victusfate/scaffold/prune)<a href="https://agentmods.dev/skills/victusfate/scaffold/prune"><img src="https://agentmods.dev/badge/skills/victusfate/scaffold/prune/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/victusfate/scaffold/prune"><img src="https://agentmods.dev/badge/skills/victusfate/scaffold/prune.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.00039 | $0.00088 |
| Opus 5.5 | $0.00016 | $0.00035 |
| Sonnet 5.5 | $0.00008 | $0.00018 |
| Haiku 4.5 | $0.00004 | $0.00009 |
Grade A, and why
prune 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 1mo 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
Read and follow the complete skill instructions in skills/prune.md.
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.
- 1mo ago First seen · 12 lines · 39 tokens per session scan A c69241f71501
prune is a skill published in the GitHub repository victusfate/scaffold (6 stars, last pushed 8d ago), licensed MIT. It adds 39 tokens to every session and 88 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-08-31.
Other skills, from other repositories
engineering-workflow
A Chinese-language workflow for reliable software development. It describes exploring the problem, making a plan, using TDD (test-driven development, where tests are written before the code), debugging methodically, reviewing code, and verifying the result.
review
Review a small code change for correctness and missing tests.
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
Pair Programming
AI-assisted pair programming with multiple modes (driver$navigator$switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
coding
Use when five specialized coding agents (linter, perf, refactor, security, test) that enforce quality gates across the development lifecycle. From lint enforcement through performance profiling, refactoring, security auditing, and test coverage. Use when working with coding agents.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.