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 tzachbon/smart-ralph --skill speckit-workflowgit clone --depth 1 https://github.com/tzachbon/smart-ralphWrote 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/tzachbon/smart-ralph/speckit-workflow)<a href="https://agentmods.dev/skills/tzachbon/smart-ralph/speckit-workflow"><img src="https://agentmods.dev/badge/skills/tzachbon/smart-ralph/speckit-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/tzachbon/smart-ralph/speckit-workflow"><img src="https://agentmods.dev/badge/skills/tzachbon/smart-ralph/speckit-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.01855 |
| Opus 5.5 | $0.00012 | $0.00742 |
| Sonnet 5.5 | $0.00006 | $0.00371 |
| Haiku 4.5 | $0.00003 | $0.00186 |
Grade A, and why
speckit-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 1mo 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecKit Workflow
The SpecKit methodology is a constitution-driven approach to feature development. It ensures consistency across features by grounding all decisions in project principles.
Core Philosophy
Constitution First: Every feature is designed against the project's constitution - a living document of principles, constraints, and standards.
Governance Over Convention: Rather than implicit patterns, SpecKit makes governance explicit through:
- Constitution principles (MUST, SHOULD, MAY)
- Feature specifications tied to principles
- Quality checklists as "unit tests for requirements"
- Consistency analysis across artifacts
Directory Structure
.specify/
├── memory/
│ └── constitution.md # Project principles and standards
├── .current-feature # Active feature pointer
├── templates/ # Artifact templates
│ ├── spec-template.md
│ ├── plan-template.md
│ ├── tasks-template.md
│ └── checklist-template.md
└── specs/
└── <id>-<name>/ # Feature directories
├── .speckit-state.json
├── .progress.md
├── .coordinator-prompt.md
├── spec.md # Feature specification
├── plan.md # Technical design
├── tasks.md # Implementation tasks
├── research.md # Research findings (optional)
├── data-model.md # Entity definitions (optional)
├── contracts/ # API contracts (optional)
└── checklists/ # Quality checklists
Feature ID System
Features use auto-incremented 3-digit IDs:
001-user-auth002-payment-gateway003-notification-system
Benefits:
- Natural ordering in filesystem
- Easy reference in commits/PRs
- Prevents naming conflicts
Workflow Phases
Phase 1: Constitution (/speckit:constitution)
Establish or update project-wide principles.
Inputs: Project context, team preferences
Outputs: .specify/memory/constitution.md
Constitution sections:
- Identity: Project name, purpose, core domain
- Principles: MUST/SHOULD/MAY rules
- Technology Stack: Languages, frameworks, tools
- Patterns: Architecture, naming, error handling
- Quality Standards: Testing, performance, security
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.
- 1mo ago First seen · 269 lines · 30 tokens per session scan A e87350469cf3
speckit-workflow is a skill published in the GitHub repository tzachbon/smart-ralph (562 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,855 once invoked, about $0.0001 per session on Opus 5.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
omc-plan
Strategic planning with optional interview workflow.
ultragoal
Durable multi-goal workflow that persists plan/ledger artifacts under .omc/ultragoal and prints Claude /goal handoff text for the active session.
orchestrator-lanes
Terminal Lane Stack Claude Code dev-orchestrator only (run-controller harness: score, DAG, run-supervisor, L0/L1/L2, wt-merge-main). Use when the session runs that terminal harness, or when $ARGUMENTS is exactly info. SKIP: Lane Pilot / BB chats (dispatch there is lanepilotdispatchwriter, LANEPILOTAGENTTYPE set)…
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
resume-project
A project-resume skill for starting work on an existing repository after a pause or a new session. It reports the current state, blockers, and next actions.
drmax-brandcore
A company facts file and guided process for recording approved claims, products, legal details, and other information that content agents may use. It acts as a single source of truth instead of letting later content generation guess.