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 savegit 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/save)<a href="https://agentmods.dev/skills/victusfate/scaffold/save"><img src="https://agentmods.dev/badge/skills/victusfate/scaffold/save/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/save"><img src="https://agentmods.dev/badge/skills/victusfate/scaffold/save.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.00090 | $0.00137 |
| Opus 5 | $0.00045 | $0.00068 |
| Sonnet 5 | $0.00018 | $0.00027 |
| Haiku 4.5 | $0.00009 | $0.00014 |
Grade A, and why
save 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 6d 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/save.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.
- 6d ago First seen · 12 lines · 90 tokens per session scan A 6ec25178f22c
save is a skill published in the GitHub repository victusfate/scaffold (6 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 137 once invoked, about $0.0005 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-04.
Other skills, from other repositories
commit
Create git commits with good messages. Use when user says "commit", "create commit", or asks to commit changes.
release-notes
Draft a release note section from a commit range, grouped by what the reader gets.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
git-flow
Use this skill when proposing, reviewing, or troubleshooting git commits, branches, pull requests, or merge strategies in a WrongStack project session. Triggers: user mentions "commit", "branch", "PR", "merge", "rebase", "stash", "diff".
prepare-pr
End-to-end drives working-tree changes to a review-ready pull request — commit, sync base, squash to one commit, open/update the PR — then KEEPS RUNNING IN-SESSION (poll CI + code-review bots in 5-min rounds, up to 10) fixing every legitimate Critical/High finding and build failure until the PR is review-ready (never…
commit
Atomic git commit with conventional message. Use when the user says "commit", "save my changes", "commit this", or wants to create a git commit. Stages specific files, writes a conventional commit message with body explaining non-obvious decisions. Never uses git add -A.