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 boshu2/agentops --skill validategit clone --depth 1 https://github.com/boshu2/agentopsWrote 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/boshu2/agentops/validate)<a href="https://agentmods.dev/skills/boshu2/agentops/validate"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/validate/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/boshu2/agentops/validate"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/validate.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.00043 | $0.01552 |
| Opus 5.5 | $0.00017 | $0.00621 |
| Sonnet 5.5 | $0.00009 | $0.00310 |
| Haiku 4.5 | $0.00004 | $0.00155 |
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 20d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate
Independently judge one exact subject against the acceptance in its existing
bead or caller source, return one semantic result, and stop. Validate is the
sole verdict.v2 writer when persistence is requested. It never asks the model
to reconstruct Plan or Candidate packets.
Preconditions
- The subject is a nonempty implementation candidate: the manifest lists at
least one entry, and
store-verdictrefuses an empty one. Plans, audits, reviews, and other control artifacts are not completion subjects unless the caller explicitly requested document review. - The intent source is available as a caller-owned artifact or runtime-owned content-addressed snapshot; its acceptance digest is derived automatically.
- The subject manifest still matches the subject.
- Author and validator context IDs are explicit.
- Freshness is explicitly attested with
source: runtime | callerand an attester identity.
Missing, colliding, or unattested identities produce NOT_PROVEN. This is a
declared trust fact, not cryptographic proof that contexts were isolated.
Cross-model fresh validator (caller-elected)
A caller may request that the fresh validator run on a different model than
the author. Dispatch via the controller-session recipe in
the agent-native model-dispatch recipe (codex-exec and/or NTM panes,
probed at runtime). Record author and validator model_identity in evidence
refs and freshness attestation notes — do not change verdict.v2 schema. If
the requested validator model has no live adapter, disclose the unsatisfied
diversity request and proceed same-model. Single fresh validator remains the
default shape.
Mutating-check quarantine
Before running any acceptance-listed command, classify it as read-only or
subject-mutating. Regen scripts, sync scripts, formatters, and anything with
--force are subject-mutating until proven otherwise. Never run a
subject-mutating check against an uncommitted subject: on 2026-07-15,
scripts/test-ci-deterministic-gates.sh regenerated skills-codex/ from HEAD
mid-validation and destroyed the uncommitted subject, forcing NOT_PROVEN
(verdict b6e759dd...cb6a); only restoring the subject and revalidating in a
fresh context produced the PASS (e9b6cdb8...37b9). If a mutating check is
genuinely required by acceptance, run it against a disposable copy or a
committed subject, never the judged working tree.
What ships with it
5 files 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.
- 20d ago Changed · -24 lines · +9 tokens per session 799a90844a24
- 23d ago Changed · +17 lines · -2 tokens per session a8df0a203f54
- 1mo ago Changed · +20 lines · -19 tokens per session b9b184792292
- 1mo ago Changed · -78 lines ba44309cd70c
- 1mo ago Changed · +19 lines · +5 tokens per session fb6318f47dca
- 1mo ago Changed · +21 lines 9f0e8c7e4270
- 1mo ago Changed · +16 lines c212691f354d
- 1mo ago First seen · 151 lines · 50 tokens per session scan A 3f986a485a94
validate is a skill published in the GitHub repository boshu2/agentops (448 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 1,552 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
libfuzzer
Use when asked to build, run, or triage a coverage-guided C/C++ fuzz campaign on the libFuzzer or AFL++ engine. Not for harness design: use fuzz-harness-writing.
strict-validation-setup
Use when a user invokes a strict-mode validation or verifiable-goals loop setup. Bootstraps strict-mode tooling and per-task GOALS.md scaffolding so an agentic loop can self-verify. Don't use for remote, credential, publish, deploy, or irreversible changes.
atheris
Use when a user needs coverage-guided fuzzing for Python code or a Python native extension using Atheris. Not for remote, credential, publish, deploy, or irreversible changes.
fuzzing
Use when planning an end-to-end fuzzing program for a project: engine and target selection, corpus management, and CI or nightly wiring. Not for harness design: use fuzz-harness-writing. Not for engine operation or triage: use libfuzzer. Not for sanitizer flag reference: use sanitizers.
oss-fuzz
Use when enrolling a project in OSS-Fuzz, running its helper workflow locally, or reproducing an OSS-Fuzz report. Not for remote, credential, publish, deploy, or irreversible changes.
validation-first-driven
Use when building protocols, workflows, concurrent systems, or lifecycle-heavy state that needs explicit states, transitions, and temporal properties. Defines the state machine, encodes invariants in types, and for high-risk designs runs a TLA+ or Alloy model checker. Not for encoding domain models in types — use…