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 VonTerraProject501c3/slushpile --skill statusgit clone --depth 1 https://github.com/VonTerraProject501c3/slushpileWrote 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/vonterraproject501c3/slushpile/status)<a href="https://agentmods.dev/skills/vonterraproject501c3/slushpile/status"><img src="https://agentmods.dev/badge/skills/vonterraproject501c3/slushpile/status/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/vonterraproject501c3/slushpile/status"><img src="https://agentmods.dev/badge/skills/vonterraproject501c3/slushpile/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.02781 |
| Opus 5 | $0.00029 | $0.01391 |
| Sonnet 5 | $0.00012 | $0.00556 |
| Haiku 4.5 | $0.00006 | $0.00278 |
Grade A, and why
status 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 10d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status
Every other skill in this pipeline writes application.yaml. This one reads them all back.
Two questions, answered together on purpose:
Where does the search stand? What is in flight, what is waiting on the user, what has gone silent past the point of hope, and which of the assessed-not-applied roles is worth the next slot.
Is the pipeline any good? The regression of what the review predicted against what actually happened. A pipeline that grades most applications INTERVIEW and converts five percent is not producing signal, it is producing optimism, and nothing else in the system will ever contradict it.
Announce at start: "Reading every application.yaml in the workspace. Reporting queue state and pipeline calibration."
Arguments:
$1— optional. A company name or a path, to narrow the report. With nothing, the whole workspace.
Example:
/slushpile:status
/slushpile:status Acme
Why Calibration Lives Here
The calibration regression was originally its own command, run monthly. It did not get run.
A maintenance ritual with no forcing function competes against whatever the user actually opened the terminal to do, and it loses every time — most reliably when the pipeline is drifting, because a drifting pipeline is one that keeps saying encouraging things. Folding it into the command someone runs to see their queue means the drift arrives whether or not they asked for it.
The cost is that this skill does two jobs. That is the intended trade.
Prerequisites
applications/**/application.yaml— the corpus. Everything here is read from these.job_search.md— the tracker, and where the calibration table is written backpreferences.yaml— forcalibration_priors, which this skill maintains
If no application.yaml files exist, say so and stop. There is nothing to report on and a status page assembled from zero records looks the same as one assembled from a healthy search.
Phase 1: Read the Corpus
Find every application.yaml under applications/. Read each one.
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.
- 10d ago First seen · 173 lines · 58 tokens per session scan A ba3e608574cb
status is a skill published in the GitHub repository VonTerraProject501c3/slushpile (15 stars, last pushed 24d ago), licensed MIT. It adds 58 tokens to every session and 2,781 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-08-30.
Other skills, from other repositories
recipe-plan
Create work plan from design document and obtain plan approval.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
recruit-init
Uma habilidade que prepara um espaço de trabalho para recrutamento, com pastas, documentos de referência, registros e instruções para agentes de programação. Ela verifica dependências como Node.js, ferramentas de vagas e, opcionalmente, o Feishu.
job
Daily routines for a corporate software engineering job. Start mode triages the inbound review queue, your own open PRs, and the issue tracker's plan for today. End mode clears the outbox, surfaces review debt, sweeps worktrees for unpushed work, and tidies tracker state for tomorrow. Use via /job, /job start, /job…
freehire-mail-triage
Use when sorting a job seeker's application mail into the freehire tracker from their own mail client (himalaya, mbsync, notmuch, the Gmail API, any IMAP) — pushing a fetched batch, judging what each message is, linking it to an application, advancing a stage from a reply, or draining the two queues the matcher fills…