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/JairoTorregrosa/jaiskillsWrote 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/jairotorregrosa/jaiskills/constatar-verify)<a href="https://agentmods.dev/commands/jairotorregrosa/jaiskills/constatar-verify"><img src="https://agentmods.dev/badge/commands/jairotorregrosa/jaiskills/constatar-verify/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/jairotorregrosa/jaiskills/constatar-verify"><img src="https://agentmods.dev/badge/commands/jairotorregrosa/jaiskills/constatar-verify.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.00011 | $0.00216 |
| Opus 5 | $0.00005 | $0.00108 |
| Sonnet 5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
constatar-verify 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 10d 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
Run ad-hoc rung-1 verification through the constatar engine so the evidence is journaled and grounded (never self-assessed).
- Parse
$ARGUMENTS: unit name, then oracle commands (split on--; if the user gave none, derive the project's canonical gate: test + lint + build commands from the repo's tooling). constatar verify --unit <name> --run-dir .constatar-adhoc --cwd . --cmd <c1> --cmd <c2> ...- Report the evidence JSON: pass/fail per command with exit codes. A non-zero exit is a FAIL to report verbatim — never soften it.
- For verification beyond rung 1 (adversarial/judge), tell the user to declare it in a plan.toml (see the constatar-plan skill) — ad-hoc CLI verification is rung 1 only.
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.
- 10d ago First seen · 12 lines · 11 tokens per session scan A e96c336796f5
constatar-verify is a command published in the GitHub repository JairoTorregrosa/jaiskills (5 stars, last pushed 9d ago), licensed MIT. It adds 11 tokens to every session and 216 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-31.
Other commands, from other repositories
lavra-qa
Browser-based QA verification of the running app -- systematic testing from the user's perspective.
test-browser
Run browser tests on pages affected by current PR or branch.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
pn-audit-design-tokens
Surgical design-token audit — CSS custom property coverage, token naming, dark-mode correctness, and hardcoded value elimination. Standalone or chained by pn-frontend-audit.
add-specs
Add specs using a structured testing approach.
add-tests
Add tests using a structured testing approach.