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/adamwstauffer/shidlerWrote 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/commands/adamwstauffer/shidler/readme)<a href="https://agentmods.dev/commands/adamwstauffer/shidler/readme"><img src="https://agentmods.dev/badge/commands/adamwstauffer/shidler/readme.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.1 | $0.00000 | $0.00525 |
| Opus 5 | $0.00000 | $0.00262 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
README 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 7d 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
Slash Commands
Repo-tailored slash commands for this course-materials repo. Cherry-picked and retargeted from
the LiosAg/farm-management-assistant-v2 workflow layer — see
docs/decisions/2026-07-12-claude-workflow-commands-cherry-pick.md for the rationale and the
per-command tweaks.
Commands with real procedure delegate to a paired skill in .claude/skills/<name>/; the command
file is the thin entry point (what it does, args, output).
| Command | Purpose | Skill | Model |
|---|---|---|---|
/breakpoint |
Session pickup prompt before a context break — captures branch/PR/grading state, persists to docs/breakpoints/ |
breakpoint |
session |
/suggest-optimal |
One-shot verify-then-pushback review of a converged proposal; returns THE optimal call | — | Fable → Opus |
/grill-me |
Sequential one-question-at-a-time convergence before a memo/restructure/rubric; Auto-Pushback + Repo Convergence Check | grill-me |
Fable |
/decision-memo |
Author a docs/decisions/ memo to house standard (grep-prior-first, house format, pause for ratification) |
— | Fable |
/claude-md-audit |
Periodic drift scan of CLAUDE.md + the memory store (stale refs, contradictions, bloat) | claude-md-audit |
session |
/memory-hygiene |
Validate + organize the Claude auto-memory store (validate_memory.py) |
memory-hygiene |
session |
/design-critique |
Brand-anchored critique of UH Mānoa-branded materials against docs/_branding/design.json |
design-critique |
session |
Model routing
/suggest-optimal, /grill-me, and /decision-memo are Fable-pinned (via each command's
model: frontmatter) because they are judgment-dense and their output is canonical or
hard-to-reverse. /suggest-optimal falls back to Opus (/model claude-opus-4-8) if Fable is
unavailable. The rest run on the session model — they're mechanical. This mirrors the source
repo's §10 Model Routing convention; the pins are optional and can be removed if undesired.
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.
- 7d ago First seen · 28 lines · 0 tokens per session scan A 1de8316900bb
README is a command published in the GitHub repository adamwstauffer/shidler (10 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 525 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.