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/ThibautBaissac/rails_ai_agentsWrote 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/thibautbaissac/rails_ai_agents/tasks)<a href="https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/tasks"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/tasks/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/commands/thibautbaissac/rails_ai_agents/tasks"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/tasks.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.00021 | $0.00627 |
| Opus 5.5 | $0.00008 | $0.00251 |
| Sonnet 5.5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
tasks 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 2mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
-
Locate feature directory: Run
.specify/scripts/bash/check-prerequisites.sh --json --paths-onlyfrom repo root. Parse JSON for FEATURE_DIR and FEATURE_SPEC. For single quotes in args, use escape syntax: e.g 'I'''m Groot' (or double-quote if possible). -
Validate spec exists: Check that FEATURE_DIR/spec.md exists. If not, abort and instruct user to run
/sdd-change:specifyfirst. -
Load context:
- REQUIRED: Read FEATURE_DIR/spec.md (the change spec)
- IF EXISTS: Read
.specify/memory/constitution.mdto respect project principles - IF EXISTS: Read
.specify/memory/lessons-learned.md— filter to entries tagged[phase:implement]or[phase:all]
-
Load task template: Read
.specify/templates/change-tasks-template.mdfor the required flat format. -
Generate tasks from the change spec:
Extract from the spec:
- The Problem and Proposed Change (what needs to happen)
- The Acceptance Criteria (what must be verified)
- The Files Likely Affected (where to make changes)
Generate tasks in this order:
- Migration/schema tasks (if database changes needed)
- Implementation tasks (one per file or logical unit of change)
- Test tasks (write or update specs for changed behavior)
- Validation task (always last):
Run bundle exec rspec && bundle exec rubocop -a
Task format rules:
- Format:
- [ ] T001 Description with exact file path - Sequential numbering: T001, T002, T003...
- No
[P]markers (tasks are always sequential) - No
[US#]markers (no user stories in the lightweight pipeline) - Include exact file paths in every task description
- Minimum 3, maximum 8 tasks
If the change requires more than 8 tasks, warn the user: "This change may need the full
/sdd:taskspipeline for proper phase-based task organization." Wait for confirmation.
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.
- 2mo ago First seen · 59 lines · 21 tokens per session scan A acb46ea27d1c
tasks is a command published in the GitHub repository ThibautBaissac/rails_ai_agents (672 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 627 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.
tasks compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| tasksThibautBaissac/rails_ai_agents | Command | 672 | 5mo ago | MIT | A | 21 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |