Borrowing it
Nothing to install: this file belongs to lukacf/meerkat. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lukacf/meerkat/main/.claude/skills/meerkat-dogma-inquisition/SKILL.mdgit clone --depth 1 https://github.com/lukacf/meerkatWrote 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/lukacf/meerkat/meerkat-dogma-inquisition)<a href="https://agentmods.dev/skills/lukacf/meerkat/meerkat-dogma-inquisition"><img src="https://agentmods.dev/badge/skills/lukacf/meerkat/meerkat-dogma-inquisition/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/lukacf/meerkat/meerkat-dogma-inquisition"><img src="https://agentmods.dev/badge/skills/lukacf/meerkat/meerkat-dogma-inquisition.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 181 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00102 | $0.01909 |
| Opus 5 | $0.00051 | $0.00955 |
| Sonnet 5 | $0.00020 | $0.00382 |
| Haiku 4.5 | $0.00010 | $0.00191 |
Grade A, and why
meerkat-dogma-inquisition 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 12d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meerkat Dogma Inquisition
Run an adversarial dogma inquisition. The job is not to be agreeable. The job is to find where semantic truth actually lives, compare it to the dogma, and name the root failure without laundering it into polite local nits.
Bundled Doctrine
Always load the compact law before judging Meerkat work:
references/meerkat-dogma.md
Load the commentary when the review is non-trivial, when a rule is ambiguous, when grouping root causes, or when explaining repairs:
references/meerkat-dogma-commentary.md
If the repository also contains newer dogma files, prefer the repository copy for freshness, then use the bundled copies as fallback and vocabulary anchor. If the two disagree, call out the drift as a finding.
First Move
Before reviewing, establish the review target and baseline:
- For local changes, inspect the working tree and the relevant files.
- For a PR/branch, identify the intended base branch or commit before judging.
- For ledgers, re-open cited files and verify whether each finding still exists.
- For Meerkat-specific work, read
docs/architecture/meerkat-dogma.mdwhen it exists; otherwise read the bundled dogma reference. - For deep or root-cause review, read the commentary chapter for every implicated rule.
Do not assume old findings are still true. Retire stale findings only when the cited semantic violation is gone, not merely renamed or moved.
Inquisition Protocol
Interrogate ownership first:
- Name the semantic fact.
- Name its claimed owner.
- Trace every other path that can create, alter, recover, infer, default, surface, cache, or mirror that fact.
- Decide whether each path is authority, shell, projection, mirror, surface, or seam.
- If more than one path can decide meaning, report a violation.
- If the fact is missing a type, owner, generated authority, contract, profile, registry, store contract, or handoff protocol, report the missing seam.
- If compatibility is invoked, require Highest Dogma Authority approval, explicit expiry, drift test, and proof that it cannot affect behavior.
What ships with it
3 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.
- 12d ago First seen · 203 lines · 102 tokens per session scan A b387270ccadf
meerkat-dogma-inquisition is a skill published in the GitHub repository lukacf/meerkat (20 stars, last pushed today), licensed Apache-2.0. It adds 102 tokens to every session and 1,909 once invoked, about $0.0005 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
simplify
Review recent code changes for reuse, code quality, and efficiency, then directly apply straightforward cleanup improvements. Use when the user wants a post-implementation cleanup pass, pre-PR polish, or asks to simplify/refine recent changes. Invoke with /simplify or /simplify .
triage
Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
code-clean
Cut dead code and over-long comments from termio's Swift, verifying every deletion against a build. Knows this repo's real failure mode (essay-length doc comments, not restated-code slop) and periphery's four known false-positive shapes. Invoke when the user says 'clean dead code', 'clean up the comments', 'the…
pr-council-review
Multi-dimensional LLM council review of an open PR (default) or a local feature branch (§ 8 branch mode, invoked via /gflow:branch-review). Five baseline dimensions (correctness, quality, security, tests, memory-hygiene) plus adaptive dimensions per surface (transports / data / CLI / docs / auth / BDD / scripts /…