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/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/thoughtbot/rails-consultant/standup"><img src="https://agentmods.dev/badge/skills/thoughtbot/rails-consultant/standup.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.00037 | $0.01135 |
| Opus 5.5 | $0.00015 | $0.00454 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 111 lines · 37 tokens per session scan A 9c289e430c04
standup is a skill published in the GitHub repository thoughtbot/rails-consultant (26 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,135 once invoked, about $0.0001 per session on Opus 5.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
work
Execute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
plan
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
csift
Reads, searches and counts Claude Code session transcripts (the .jsonl files under /.claude/projects, subagents too) with the csift command-line tool, and ships hooks that re-inject compacted turns or record pending questions. Use when asked what a past or running session said, did, edited, spent or is doing now; when…
recursive-decomposition
Decompose dense codebase-wide, multi-document, PDF, and aggregation work even when the input fits the context window, following Recursive Language Models (Zhang, Kraska, Khattab, 2025). Use when the user asks to analyse all files, a whole repo, all docs, large PDFs, or to aggregate or multi-hop across scattered…