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.
git clone --depth 1 https://github.com/854771076/oh-my-claude-rolesWrote 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/854771076/oh-my-claude-roles/validate-prompt-spec)<a href="https://agentmods.dev/commands/854771076/oh-my-claude-roles/validate-prompt-spec"><img src="https://agentmods.dev/badge/commands/854771076/oh-my-claude-roles/validate-prompt-spec/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/commands/854771076/oh-my-claude-roles/validate-prompt-spec"><img src="https://agentmods.dev/badge/commands/854771076/oh-my-claude-roles/validate-prompt-spec.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.00016 | $0.00395 |
| Opus 5 | $0.00008 | $0.00198 |
| Sonnet 5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
validate-prompt-spec 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 11d 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.
What it actually says
命令内容
对指定路径的提示词文件进行企业级规范合规性检查，输出完整的检查报告和修复建议。
目标文件：$ARGUMENTS
执行步骤：
- 读取目标提示词文件及其配套的Zod Schema文件
- 对照《AI提示词开发企业级规范》检查以下维度：
- 结构完整性：是否包含8个核心模块（角色定位、核心目标、执行规则、输入规范、输出规范、约束与禁忌、异常处理规则、参考示例）
- 类型安全：是否正确定义了输入输出Zod Schema，是否实现了输入前置校验和输出二次校验
- 技术栈合规：是否使用了企业指定首选技术栈，是否存在禁用方案
- 安全合规：是否包含输入输出防护、注入攻击拦截、敏感信息管控规则
- 禁忌红线：是否违反禁止硬编码敏感信息、模糊描述、突破约束等强制红线
- 输出结构化检查结果，列出合规项、违规项、清晰的修复建议
- 如果无严重违规，给出规范合规结论
检查要点：
- 必须覆盖规范所有强制要求项，不能遗漏
- 违规项必须标注对应规范条款编号
- 修复建议必须具体可执行，符合规范要求
- 严重违规必须明确标注，禁止合并上线
---
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.
- 11d ago First seen · 33 lines · 16 tokens per session scan A 0cfc77ba7ffc
validate-prompt-spec is a command published in the GitHub repository 854771076/oh-my-claude-roles (22 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 395 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.