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 thoughtbot/rails-consultant --skill standupgit clone --depth 1 https://github.com/thoughtbot/rails-consultantWrote 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/thoughtbot/rails-consultant/standup)<a href="https://agentmods.dev/skills/thoughtbot/rails-consultant/standup"><img src="https://agentmods.dev/badge/skills/thoughtbot/rails-consultant/standup.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.00037 | $0.01135 |
| Opus 5 | $0.00018 | $0.00567 |
| Sonnet 5 | $0.00007 | $0.00227 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
standup 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Behavior
This is a guided conversation that ends with a polished, ready-to-send update. Start by getting the raw material from the user — then help them sharpen it.
Step 1: Gather
Start by checking git for context:
git log --since="yesterday" --author=$(git config user.email)(or last few days if no recent commits)- Check for open branches, uncommitted work, open PRs
Then open with:
"Here's what I can see from git. Before I help you write this — what did you actually spend your time on? Git doesn't always tell the full story."
Wait for their answer. Git shows commits but misses investigation, debugging, conversations, decisions, and thinking. Their answer fills the gaps.
Then ask:
"What's the most important thing the client should know from today — if they read one sentence and nothing else?"
Wait. This forces them to prioritise. Most updates bury the lead.
Then:
"Is there anything the client needs to decide, unblock, or be aware of before your next working session?"
Wait. This surfaces blockers and risks before they become surprises.
Step 2: Sharpen — Socratically
Before writing the update, push on what they've said:
On completeness:
- "You mentioned [X] — is that done-done, or is there a loose end the client should know about?"
- "Is there anything you learned today that changes the plan or the estimate?"
- "Are you waiting on anything from the client's side? Now's the time to ask — don't let it sit."
On risks — push hard here:
- "Is there a risk here you're not mentioning because you think you can handle it? Those are the ones worth flagging early."
- "If the client asked 'are we on track?' right now — what's your honest answer?"
- "Are you going to hit the next deadline? If there's any doubt, say it now — not the day before."
- "Is there anything that took longer than expected today? If so, does that change the timeline for what comes next?"
- "Are there areas you shipped without full test coverage? What's the QA gap — and does the client know?"
- "Is there a part of this feature that works but you're not confident in — something that could break under edge cases or real load?"
- "Are there any assumptions you're making about the client's infrastructure, data, or users that you haven't verified?"
- "If you got hit by a bus tomorrow, what would fall through the cracks?"
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 · 111 lines · 37 tokens per session scan A 9c289e430c04
standup is a skill published in the GitHub repository thoughtbot/rails-consultant (24 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,135 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 skills, from other repositories
archive-issue
Retire a closed issue's working artifacts out of specs/ into the GitHub wiki. Use only when the user asks to archive a finished issue, empty out specs/ for a done task, or move an issue's requirements/architecture/tasks/review/QA docs to the wiki.
start-task
Bootstrap a task into a synced feature branch — one shot, zero confirmations. Detects the source from the args: GitHub issue ('#100', 'issue 100', 'gh issue 100', or bare '100'), Jira key ('PROJ-42'), or a local spec file path; ad-hoc conversation otherwise. Fetches the task, derives {type}/{number}/{slug}, syncs the…
abd-status
ABD Status agent: read-only dashboard of tasks, findings by severity, blockers, and next actions across all handoff artifacts.
sprint-plan
Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs.
dev-story
Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before…
retrospective
Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.