Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jaroslavsoucek-art/Giovanni/plugin install giovanniWrote 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/jaroslavsoucek-art/giovanni/consistency-check)<a href="https://agentmods.dev/skills/jaroslavsoucek-art/giovanni/consistency-check"><img src="https://agentmods.dev/badge/skills/jaroslavsoucek-art/giovanni/consistency-check/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/jaroslavsoucek-art/giovanni/consistency-check"><img src="https://agentmods.dev/badge/skills/jaroslavsoucek-art/giovanni/consistency-check.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.00052 | $0.01968 |
| Opus 5.5 | $0.00021 | $0.00787 |
| Sonnet 5.5 | $0.00010 | $0.00394 |
| Haiku 4.5 | $0.00005 | $0.00197 |
Grade A, and why
consistency-check 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 today.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/giovanni:consistency-check
Run the 8 semantic invariants that deterministic ${CLAUDE_PLUGIN_ROOT}/scripts/lint.sh cannot reach (memory↔constitution drift, decisions↔constitution drift, agent roster description mismatch, topic shard cross-reference breakage, optional architecture audit staleness, decided-terms completeness, knowledge↔knowledge cross-doc drift, published-pages outbound drift). This command is a thin shell — checks and report format live in the giovanni:consistency-checker agent. This file is the invocation contract.
Usage
/giovanni:consistency-check # all enabled checks
/giovanni:consistency-check --check <id> # single check
/giovanni:consistency-check --since <YYYY-MM-DD> # narrows git-log scan window for staleness checks
/giovanni:consistency-check --write # commit findings to file (default = also writes; flag is reserved for future render-only mode)
Valid --check ids:
memory-blockers-vs-constitutiondecisions-vs-constitutionagent-roster-semantictopic-shard-stakeholder-xrefaudit-staleness(optional — only if fork uses architecture tier audits)decided-terms-completeness(no-op with INFO ifmemory/audits/consistency/decided-terms.yamlis absent)
Argument syntax
| Arg | Type | Default | Meaning |
|---|---|---|---|
--check <id> |
parameterized | all | Run a single check by ID instead of all enabled checks. |
--since <YYYY-MM-DD> |
parameterized date | 30 days ago | For staleness check (audit-staleness): limits the git-log window. Ignored by other checks. |
--write |
boolean flag | implicit (always writes report) | Reserved for future render-only mode. Default behavior writes the report file. |
Pre-flight (binding — STOP on failure)
Before spawning giovanni:consistency-checker:
- CWD check. Working directory is a Giovanni repo (presence of
memory/CLAUDE_MEMORY.md+knowledge/<constitution>.md). Otherwise STOP. - Agent definition present.
${CLAUDE_PLUGIN_ROOT}/agents/consistency-checker.mdexists. Missing → STOP. - Audit directory present.
memory/audits/consistency/exists. Create if missing (this is the only directory the orchestrator creates pre-spawn). - State file present.
memory/audits/consistency/_state.mdexists with a non-emptyshadow_mode_start_datefield. If missing or empty:- Auto-seed: set
shadow_mode_start_date = today,shadow_mode_end_date = today + 28 days. - Surface advisory:
INFO: seeded shadow mode 28d from today. Score precision before promoting to operational warnings.
- Auto-seed: set
- Constitution + L1 present.
knowledge/<constitution_file>.md(perdocs/governance.config.yaml) andmemory/CLAUDE_MEMORY.mdexist. Missing → STOP — the checks have no input.
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.
- today First seen · 120 lines · 52 tokens per session scan A 04a3b95ba978
consistency-check is a skill published in the GitHub repository jaroslavsoucek-art/Giovanni (2 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,968 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-10-17.
Other skills, from other repositories
continuum-observability
Trace agent runs with Langfuse, decorate functions with @observe, collect latency/token/error metrics, and report errors. Invoke when the user asks about "see what the LLM was prompted with", "Langfuse traces", "track latency", "metrics dashboard", "error reporting", or "instrument my function".
Debug Snapshot
Capture the host's environment, working directory, recent git activity, and pipeline-relevant state so you can diagnose "what's actually happening on the machine".
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
triage-issue
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
hive.error-recovery
Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.
skill-repair
Diagnose and fix failing or degraded skills automatically - systemic-first triage, per-category playbooks, and a verification plan.