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 agents/iansmith/slopstop/slopstop-effort-mediumgit clone --depth 1 https://github.com/iansmith/slopstopWrote 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/iansmith/slopstop/slopstop-effort-medium)<a href="https://agentmods.dev/agents/iansmith/slopstop/slopstop-effort-medium"><img src="https://agentmods.dev/badge/agents/iansmith/slopstop/slopstop-effort-medium.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.00054 | $0.00201 |
| Opus 5 | $0.00027 | $0.00101 |
| Sonnet 5 | $0.00011 | $0.00040 |
| Haiku 4.5 | $0.00005 | $0.00020 |
Grade A, and why
slopstop-effort-medium 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 15 lines · 54 tokens per session scan A 4fa67a4fd475
slopstop-effort-medium is an agent published in the GitHub repository iansmith/slopstop (2 stars, last pushed 5d ago), with no licence file. It adds 54 tokens to every session and 201 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-31.
Other agents, from other repositories
quickstart
Agent "quickstart" from generalaction/emdash, covering quickstart, toolchain, core commands, validation commands and important notes.
linear-state-curator
Autonomous Linear hygiene agent. Reads every open issue across configured teams, validates true state against signals from the configured signalsources (commits in configured repos, GitHub PRs, Slack messages, Linear cross-references, plus any externalcommand sources), then auto-applies HIGH-confidence state changes…
coding-agent
Orchestrator for the issue-to-PR workflow. Given a user story ID (e.g. PROJ-1234, ENG-42.
pr-reviewer
Use for high-signal review of a diff or pull request in any codebase, with emphasis on scope (PR intent), correctness, contract drift, security, performance/duplication introduced, and the project's test/coverage gate.
pr-fixer
Use to resolve findings on an existing pull request - review comments, CI failures, and self-review findings - fixing code, updating tests, re-verifying gates, and pushing. The counterpart to pr-reviewer that closes the loop.
security-reviewer
Use for a focused security pass on a diff or pull request - authorization, secrets, input validation, data exposure, webhook verification, and OWASP-style concerns. Runs as part of the coding-agent verify step and on demand.