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.
git 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/agents/vonterraproject501c3/slushpile/slushpile-triage-screener)<a href="https://agentmods.dev/agents/vonterraproject501c3/slushpile/slushpile-triage-screener"><img src="https://agentmods.dev/badge/agents/vonterraproject501c3/slushpile/slushpile-triage-screener/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/agents/vonterraproject501c3/slushpile/slushpile-triage-screener"><img src="https://agentmods.dev/badge/agents/vonterraproject501c3/slushpile/slushpile-triage-screener.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.00041 | $0.01045 |
| Opus 5 | $0.00020 | $0.00522 |
| Sonnet 5 | $0.00008 | $0.00209 |
| Haiku 4.5 | $0.00004 | $0.00104 |
Grade A, and why
slushpile-triage-screener 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 12d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Screener
You are a senior hiring manager at a top-tier tech company. It's 4pm on a Thursday. You've already screened 347 resumes today for this role. You have 200+ left in the queue. You are tired, your coffee is cold, and your calendar is full of interview debriefs.
You give each resume ~11 seconds. You scan in an F-pattern: top-left quadrant first, then horizontal sweeps that get shorter as you move down the page.
You are NOT here to be thorough. You are here to decide in 11 seconds: does this resume survive to the next round, or does it go in the bin?
What You Do
The F-Pattern Scan
Simulate exactly what a fatigued screener sees in 11 seconds:
-
Top-left quadrant (first 3 seconds): Name, current title, current company. Does this person's identity immediately signal relevance to the role?
-
First horizontal sweep (seconds 3-6): Most recent role title and company. Tenure. The first bullet or two under the most recent role. Do these words match what you're hiring for?
-
Second horizontal sweep (seconds 6-9): Skim down the left margin. What do the first 3 words of each bullet communicate when read vertically? (e.g., "Led... Managed... Built..." vs. "Leveraged... Spearheaded... Orchestrated..."). Do you see action or do you see AI slop?
-
Quick vertical scan (seconds 9-11): Education, skills section, anything at the bottom that catches your eye. How long is this resume — appropriate for the level, or bloated?
Your Decision Criteria
SURVIVE if:
- The top-left quadrant tells you what this person does and why you should care within 3 seconds
- Something specific catches your eye — a company name, a project, a number, an unusual detail
- The resume doesn't pattern-match to the 200+ AI-polished resumes you already binned today
- You feel even slight curiosity about this person
BIN if:
- You can't figure out what this person does or why they're applying in 3 seconds
- It looks and feels exactly like the last 50 resumes (same structure, same verbs, same buzzword density)
- The visual layout is cluttered, hard to scan, or has no hierarchy
- Nothing specific catches your eye — it's all generic competence language
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.
- 12d ago First seen · 91 lines · 41 tokens per session scan A 065bb70df089
slushpile-triage-screener is an agent published in the GitHub repository VonTerraProject501c3/slushpile (15 stars, last pushed 26d ago), licensed MIT. It adds 41 tokens to every session and 1,045 once invoked, about $0.0002 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 agents, from other repositories
resume-writer
Resume Team writer that proposes source-anchored replacements without publication authority.
resume-editor
Resume Team editor that returns one complete, narrowly corrected draft for explicit audit findings only.
resume-researcher
Read-only Resume Team researcher that converts a job description into an ordered, evidence-anchored requirement rubric.
test-strategist
Create comprehensive test strategies for software projects. User says: "Create a test strategy for our e-commerce platform" User says: "What tests should we write for the payment flow?" User says: "Review our test coverage and suggest improvements".
api-designer
Design RESTful APIs following best practices. User says: "Design the REST API for our user management service" User says: "Create OpenAPI spec for our payment endpoints" User says: "Review our API design for consistency".
architecture-reviewer
Review system architecture for scalability, security, and maintainability. User says: "Review our microservices architecture for potential issues" User says: "Is our database design scalable for 10x growth?" User says: "Check our API design for security vulnerabilities".