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 agentmods add commands/el-feo/ai-context/qa-create-stepsgit clone --depth 1 https://github.com/el-feo/ai-contextWhat 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 | $0.00012 | $0.03771 |
| Opus 5 | $0.00006 | $0.01886 |
| Sonnet 5 | $0.00002 | $0.00754 |
| Haiku 4.5 | $0.00001 | $0.00377 |
Grade A, and why
qa-create-steps 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 2d 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 — 515 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<qa_step_issue_template>
QA Step Issue Body Template
# QA Step: <Brief Description>
## Scenario
As a <role>,
Given <precondition>,
When <action>,
Then <expected outcome>
## Parent QA Issue
- QA: #<QA_NUMBER>
## Test Details
- **URL/Page:** <starting URL or page>
- **Prerequisites:** <any setup needed>
- **Test Data:** <if applicable>
## Execution Log
- [ ] Pass / Fail
- **Executed by:** (not yet executed)
- **Timestamp:** (pending)
- **Notes:** (none)
## Bugs Found
(None)
Template Field Descriptions
| Field | Description |
|---|---|
<Brief Description> |
Concise 3-8 word summary of what is being tested |
<role> |
User role or persona (e.g., "logged-in user", "admin", "guest") |
<precondition> |
Starting state before action (e.g., "I am on the dashboard page") |
<action> |
Single user action being tested (e.g., "I click the Submit button") |
<expected outcome> |
Observable result (e.g., "I should see a success message") |
<QA_NUMBER> |
Parent QA Issue number |
<URL/Page> |
Starting URL or page name |
<Prerequisites> |
Any setup required before testing |
<Test Data> |
Specific test data needed (if any) |
Given/When/Then Format Guidelines
- Given describes the initial state or preconditions
- When describes a single, atomic user action
- Then describes the expected observable outcome
- Keep each step atomic (one action per QA Step)
- Use clear, specific language that is machine-parseable
</qa_step_issue_template>
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.
- 2d ago First seen · 515 lines · 12 tokens per session scan A b267d877ed57
qa-create-steps is a command published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 3,771 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-30.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.