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 ToruAI/toru-claude-agents --skill openspec-workflowgit clone --depth 1 https://github.com/ToruAI/toru-claude-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/skills/toruai/toru-claude-agents/openspec-workflow)<a href="https://agentmods.dev/skills/toruai/toru-claude-agents/openspec-workflow"><img src="https://agentmods.dev/badge/skills/toruai/toru-claude-agents/openspec-workflow/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/toruai/toru-claude-agents/openspec-workflow"><img src="https://agentmods.dev/badge/skills/toruai/toru-claude-agents/openspec-workflow.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.00032 | $0.00729 |
| Opus 5 | $0.00016 | $0.00365 |
| Sonnet 5 | $0.00006 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
openspec-workflow 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 9d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Workflow - Specification-Driven Development
OpenSpec ensures AI agents build what was planned, not what they invented.
Directory Structure
project/
└── openspec/
├── specs/ # Source of truth (what IS built)
├── changes/ # Proposals & WIP (what SHOULD change)
├── ideas/ # Quick-capture for later
└── project.md # Project conventions
The Three-Stage Workflow
Stage 1: Proposal
Create a change proposal before implementing anything significant.
openspec/changes/add-feature-x/
├── proposal.md # What and why
├── tasks.md # Numbered implementation steps
├── design.md # Technical approach
└── specs/ # Delta specs (what will change)
Stage 2: Implementation
Work through tasks.md sequentially. Keep specs in sync with code.
Stage 3: Archive
When complete: openspec archive <change-id>
Specs merge to source of truth. Change moves to archive.
CLI Commands
# List all changes
openspec list
# Show specific change details
openspec show <change-id>
# Validate a change
openspec validate <change-id> --strict
# Archive completed change
openspec archive <change-id> --yes
# List specs
openspec spec list --long
Creating a Proposal
proposal.md format:
# Feature Name
## Summary
One paragraph: what this change does.
## Motivation
Why we need this. What problem it solves.
## Scope
- What's included
- What's explicitly NOT included
## Dependencies
- Other changes this depends on
- External requirements
tasks.md format:
# Implementation Tasks
## Phase 1: Foundation
- [ ] Task 1.1: Description
- [ ] Task 1.2: Description
## Phase 2: Core Implementation
- [ ] Task 2.1: Description
...
Rules
- Proposal before code - For anything non-trivial, write proposal.md first
- Tasks are sequential - Complete in order unless explicitly parallel
- Validate before archive -
openspec validate --strictmust pass - Specs are truth - Code follows specs, not vice versa
- Ideas are cheap - Capture in ideas/ freely, promote to changes/ when ready
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.
- 9d ago First seen · 133 lines · 32 tokens per session scan A 4de83b39158b
openspec-workflow is a skill published in the GitHub repository ToruAI/toru-claude-agents (15 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 729 once invoked, about $0.0002 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 skills, from other repositories
ln-11-plan-reviewer
Reviews an implementation plan against repository evidence before execution; identifies missing decisions and risks. Not for completed-code review.
ln-12-delivery-reviewer
Reviews a completed change for regressions, unmet acceptance, and release risks. Not for whole-codebase audits or repairs.
ln-23-test-suite-auditor
Audits existing tests for meaningful coverage, trustworthy oracles, and maintenance value. Not for test implementation or a single delivery review.
ln-21-documentation-auditor
Audits documentation and comments for trustworthy claims, coverage, and discoverability. Not for code, test, or architecture audits.
ln-22-codebase-auditor
Audits cross-cutting code health, security, delivery, and maintainability when no specialist audit is primary. Not for a single delivery review.
ln-24-architecture-auditor
Audits implemented architecture, boundaries, dependencies, and configuration ownership. Not for documenting current state or reviewing plans.