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/stanleykao72/claude-code-spec-workflow-odoo/spec-steering-setupgit clone --depth 1 https://github.com/stanleykao72/claude-code-spec-workflow-odooWrote 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/stanleykao72/claude-code-spec-workflow-odoo/spec-steering-setup)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/spec-steering-setup"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/spec-steering-setup.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.00000 | $0.00845 |
| Opus 5 | $0.00000 | $0.00423 |
| Sonnet 5 | $0.00000 | $0.00169 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
spec-steering-setup 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 6d 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.
This is a copy
100% identical to spec-steering-setup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Steering Setup Command
Create or update steering documents that provide persistent project context.
Usage
/spec-steering-setup
Instructions
You are helping set up steering documents that will guide all future spec development. These documents provide persistent context about the product vision, technology stack, and project structure.
Process
-
Check for Existing Steering Documents
- Look for
.claude/steering/directory - Check for existing product.md, tech.md, structure.md files
- If they exist, load and display current content
- Look for
-
Analyze the Project
- Review the codebase to understand:
- Project type and purpose
- Technology stack in use
- Directory structure and patterns
- Coding conventions
- Existing features and functionality
- Look for:
- package.json, requirements.txt, go.mod, etc.
- README files
- Configuration files
- Source code structure
- Review the codebase to understand:
-
Present Inferred Details
- Show the user what you've learned about:
- Product: Purpose, features, target users
- Technology: Frameworks, libraries, tools
- Structure: File organization, naming conventions
- Format as:
Based on my analysis, here's what I've inferred: **Product Details:** - [Inferred detail 1] - [Inferred detail 2] **Technology Stack:** - [Inferred tech 1] - [Inferred tech 2] **Project Structure:** - [Inferred pattern 1] - [Inferred pattern 2] - Ask: "Do these inferred details look correct? Please let me know which ones to keep or discard."
- Show the user what you've learned about:
-
Gather Missing Information
-
Based on user feedback, identify gaps
-
Ask targeted questions to fill in missing details:
Product Questions:
- What is the main problem this product solves?
- Who are the primary users?
- What are the key business objectives?
- What metrics define success?
Technology Questions:
- Are there any technical constraints or requirements?
- What third-party services are integrated?
- What are the performance requirements?
-
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.
- 6d ago First seen · 112 lines · 0 tokens per session scan A 3373791eb8f0
spec-steering-setup is a command published in the GitHub repository stanleykao72/claude-code-spec-workflow-odoo (44 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 845 tokens. A static security scan graded it A with 0 findings. It is 100% identical to spec-steering-setup, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.