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/danielpodolsky/ownyourcode/featuregit clone --depth 1 https://github.com/DanielPodolsky/ownyourcodeWhat 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.00010 | $0.05611 |
| Opus 5 | $0.00005 | $0.02805 |
| Sonnet 5 | $0.00002 | $0.01122 |
| Haiku 4.5 | $0.00001 | $0.00561 |
Grade A, and why
feature 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 yesterday.
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 — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/own:feature
⚠️ PLAN MODE WARNING: Toggle plan mode off before running this command (
shift+tab). OwnYourCode commands don't work correctly with plan mode.
Create a feature specification using Spec-Driven Development (SDD).
Overview
This command follows the SDD workflow:
- AI generates the spec, design, and tasks for a phase based on minimal input
- Developer reviews them in the dashboard (the phase's Spec / Design / Tasks tabs)
- Developer adds any missing edge cases or requirements
- Then implementation begins with mentorship
Output (v2.5 — Dashboard SDD):
- The detected
roadmap-onlyphase inownyourcode/dashboard/dashboard-data.jsis advanced tospecced— itsspec,design, andtasksobjects are written in place (replacing the phase'sitems[]). Nospec.md/design.md/tasks.mdfiles; everything lives inwindow.PROJECT, rendered by the dashboard's tabs.
Schema authority:
ownyourcode/dashboard/DASHBOARD_CONTRACT.mddefines the exactspec/design/tasksshapes and the mutation rules. Read it before writing. When this command's prose and the contract disagree, the contract wins.
Profile-Aware Behavior:
Check .claude/ownyourcode-manifest.json for profile settings:
- Junior profile → Collaborative spec creation (mandatory design involvement)
- Other profiles with
design_involvement=true→ Collaborative spec creation - Profiles with
design_involvement=false→ AI generates, developer reviews
The SDD Philosophy
"Spec first, code second. But YOU own the judgment behind every line."
OwnYourCode uses SDD for planning, then builds with ownership — not by handing the junior a finished feature to read. How "build" works depends on profile:
- Junior profile → Phase 6 runs the Implementation Loop: the junior predicts the judgment for each task before the AI reveals the code, then gets graded on the prediction. They own the code by being able to evaluate it, not by transcribing it.
- Other profiles (v1) → the loop is not yet wired for them; SDD stops at the spec
and implementation happens however that developer ships.
Deliberate v1 scoping, not a permanent exclusion. The loop is built for the Junior profile first. Interview Prep is the strongest candidate to get it next — defending judgment in a live review is exactly what predict-before-reveal trains — with Career Switcher (rebuilding fundamentals) close behind. A future PR can extend Phase 6 to those profiles without contradicting this copy.
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.
- yesterday First seen · 524 lines · 10 tokens per session scan A 006c6821de35
feature is a command published in the GitHub repository DanielPodolsky/ownyourcode (276 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 5,611 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
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
version
Display current guide and Claude Code versions.
toh-help
Display all Toh Framework commands and quick usage guide.
diff-docs
Compare official Anthropic docs baseline vs current snapshot (no network — instant).
update-workflow
Regenerate an existing custom workflow's shortcut command wiring from the current swarm template.
start
Start Forge Mentor in this project — connect accounts, agree permissions, and begin the foundation interrogation.