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/o2alexanderfedin/strategic-research-automation-templateWrote 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/o2alexanderfedin/strategic-research-automation-template/validate-quality)<a href="https://agentmods.dev/commands/o2alexanderfedin/strategic-research-automation-template/validate-quality"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/validate-quality/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/o2alexanderfedin/strategic-research-automation-template/validate-quality"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/validate-quality.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.00000 | $0.00275 |
| Opus 5 | $0.00000 | $0.00138 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
validate-quality 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
Validate Quality Standards
Objective
Run quality assurance checks on sprint research and reports.
Usage
/validate-quality 01
Quality Checks
1. Citation Coverage
- Parse all research files for citations
- Calculate citation coverage percentage
- Compare against threshold in
config/quality-standards.yml - Report files with insufficient citations
2. Cross-Reference Validation
- Extract all internal markdown links
- Verify all links resolve to existing files/sections
- Report broken links
3. Terminology Consistency
- Check usage against
config/glossary.yml - Identify inconsistent term usage
- Suggest corrections
4. File Count Validation
- Count research files per task
- Verify minimum file count met (from config)
- Report tasks below threshold
5. Document Structure
- Verify each file has required sections:
- Executive Summary
- Key Findings
- Supporting Evidence
- References
- Report structural issues
6. File Size Check
- Verify files are within word count range (500-5000 words)
- Report files that are too short or too long
Output
- Quality validation report
- Pass/Fail status for each check
- List of issues with file/line references
- Recommendations for remediation
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 · 51 lines · 0 tokens per session scan A 6bd455e26203
validate-quality is a command published in the GitHub repository o2alexanderfedin/strategic-research-automation-template (19 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 275 tokens. 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
prp-plan
Create comprehensive feature implementation plan with codebase analysis and pattern extraction.
prp-prd
Interactive PRD generator - problem-first, hypothesis-driven product spec with back-and-forth questioning.
sessions
Manage Claude Code session history, aliases, and session metadata.
multi-execute
Multi-model collaborative execution - Get prototype from plan → Claude refactors and implements → Multi-model audit and delivery.
prp-implement
Execute an implementation plan with rigorous validation loops.
save-session
Save current session state to a dated file in /.claude/session-data/ so work can be resumed in a future session with full context.