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/khanh-vu/claude-force/validate-outputgit clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/khanh-vu/claude-force/validate-output)<a href="https://agentmods.dev/commands/khanh-vu/claude-force/validate-output"><img src="https://agentmods.dev/badge/commands/khanh-vu/claude-force/validate-output.svg" alt="Measured on agentmods" 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.00007 | $0.00401 |
| Opus 5 | $0.00003 | $0.00200 |
| Sonnet 5 | $0.00001 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
validate-output 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 5d 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 Output Command
Run all validators on the current .claude/work.md to ensure it meets quality standards.
Validators to Run
- Scorecard Validator - Check all scorecard items marked PASS/FAIL
- Write Zone Guard - Verify Write Zone updated correctly
- Secret Scan - Ensure no secrets in output
- Diff Discipline - Verify minimal, focused changes
- Format Lint - Validate output structure and formatting
- Hierarchy Governance - Ensure agent stayed within scope
Process
- Read
.claude/work.md - Read all validators from
.claude/hooks/validators/ - Run each validator in sequence
- Report PASS/FAIL for each
- Provide summary of issues
- Suggest remediation steps for failures
Output Format
## Validation Results
### Scorecard Validator: ✅ PASS
- All items marked PASS or justified FAIL
### Write Zone Guard: ✅ PASS
- Write Zone updated with 5 lines
- Last updated: 2025-11-13 10:30
### Secret Scan: ❌ FAIL
- Found API key on line 245
- Remediation: Replace with placeholder
### Diff Discipline: ✅ PASS
- Changes focused and minimal
### Format Lint: ✅ PASS
- All sections present
- Markdown valid
### Hierarchy Governance: ✅ PASS
- Agent stayed within contract scope
## Summary
- **Total**: 6 validators
- **Passed**: 5
- **Failed**: 1
- **Status**: ❌ VALIDATION FAILED
## Next Steps
1. Fix secret leak on line 245
2. Re-run validation
3. Proceed when all validators pass
Example
/validate-output
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.
- 5d ago First seen · 71 lines · 7 tokens per session scan A 41e84b9eb94f
validate-output is a command published in the GitHub repository khanh-vu/claude-force (5 stars, last pushed 9mo ago), licensed MIT. It adds 7 tokens to every session and 401 once invoked, about $0.0000 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-31.
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.