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 shwilliamson/automatasaurus --skill requirements-gatheringgit clone --depth 1 https://github.com/shwilliamson/automatasaurusWrote 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/shwilliamson/automatasaurus/requirements-gathering)<a href="https://agentmods.dev/skills/shwilliamson/automatasaurus/requirements-gathering"><img src="https://agentmods.dev/badge/skills/shwilliamson/automatasaurus/requirements-gathering/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/shwilliamson/automatasaurus/requirements-gathering"><img src="https://agentmods.dev/badge/skills/shwilliamson/automatasaurus/requirements-gathering.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.00028 | $0.01217 |
| Opus 5 | $0.00014 | $0.00609 |
| Sonnet 5 | $0.00006 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
requirements-gathering 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 10d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Gathering Skill
This skill provides guidance for thorough requirements gathering during discovery.
Core Principle
The more we nail down upfront, the better the results. Don't assume - ASK.
Your Job During Discovery
- Be thorough and inquisitive
- Ask clarifying questions before creating any issues
- Uncover hidden assumptions
- Define the desired end state clearly
- Identify edge cases early
- Document what's in scope AND out of scope
Questions to Ask for Every Feature
Goals & Success
- What problem are we solving?
- What does success look like? How will we measure it?
- What's the priority relative to other work?
Users & Personas
- Who are the users of this feature?
- Are there different user types with different needs?
- What permissions/roles are involved?
Core Functionality
- What is the primary goal?
- Walk me through the ideal user flow step by step
- What happens at each step?
Data & State
- What data needs to be captured/stored?
- What are the required fields vs optional?
- Are there validation rules? (formats, lengths, ranges)
- What's the initial/default state?
Edge Cases & Errors
- What happens if [X] fails?
- What if the user enters invalid data?
- What about empty states? (no data yet)
- What about concurrent access?
- Rate limiting needed?
UI/UX (if applicable)
- Is there a specific design or layout in mind?
- Mobile responsive?
- Accessibility requirements?
- Loading states? Progress indicators?
- Success/error feedback to user?
Integration
- Does this connect to external services?
- Are there existing patterns to follow?
- API format preferences?
Security & Privacy
- Is this data sensitive?
- Authentication required?
- Who can see/edit this data?
Architecture & Technical
- What's the existing tech stack?
- Are there performance requirements? (latency, throughput, scale)
- What's the deployment environment?
- Are there budget constraints?
- What external services or APIs are involved?
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.
- 10d ago First seen · 213 lines · 28 tokens per session scan A 912f963a16d9
requirements-gathering is a skill published in the GitHub repository shwilliamson/automatasaurus (5 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 1,217 once invoked, about $0.0001 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.