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 rsts-dev/claude-buddy-marketplace --skill validategit clone --depth 1 https://github.com/rsts-dev/claude-buddy-marketplaceWrote 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/rsts-dev/claude-buddy-marketplace/validate)<a href="https://agentmods.dev/skills/rsts-dev/claude-buddy-marketplace/validate"><img src="https://agentmods.dev/badge/skills/rsts-dev/claude-buddy-marketplace/validate.svg" alt="Measured on agentmods" 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.00081 | $0.00358 |
| Opus 5 | $0.00041 | $0.00179 |
| Sonnet 5 | $0.00016 | $0.00072 |
| Haiku 4.5 | $0.00008 | $0.00036 |
Grade A, and why
Validate 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 8d 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
Close the loop: run the checks and report what actually happened. Validation is the human gate before review and commit — claims of "done" mean nothing without the command output behind them.
Customization
Before executing, check ~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Validate/PREFERENCES.md. If present, load and apply it; otherwise use defaults.
Prerequisites
- buddy + LifeOS installed (
test -f ~/.claude/LIFEOS/VERSION). CLAUDE.mdand/or/directive/foundation.mdpresent (they list the validation commands). Run/sdlc:initif missing.
Workflow Routing
| Workflow | Trigger | File |
|---|---|---|
| RunValidation | Any /sdlc:validate invocation |
Workflows/RunValidation.md |
Output
A pass/fail validation report (to the conversation), with the failing output quoted verbatim.
Examples
User: "/sdlc:validate"
→ Reads validation commands from CLAUDE.md (test/lint/types/build)
→ Runs each; captures output
→ Reports PASS/FAIL per level; on failure, quotes the error and names the file
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 37 lines · 81 tokens per session scan A 7b56d2eaa5b0
Validate is a skill published in the GitHub repository rsts-dev/claude-buddy-marketplace (17 stars, last pushed 17d ago), licensed MIT. It adds 81 tokens to every session and 358 once invoked, about $0.0004 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.