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 agentmods add agents/lukacf/meerkat/a-checklistgit 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/agents/lukacf/meerkat/a-checklist)<a href="https://agentmods.dev/agents/lukacf/meerkat/a-checklist"><img src="https://agentmods.dev/badge/agents/lukacf/meerkat/a-checklist.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00564 |
| Opus 5 | $0.00000 | $0.00282 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
A-checklist 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 4d 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
Lane A Checklist
-
A-01DOGMA-08Move peer request/progress/terminal projection out of handwritten runtime ownership into a protocol or machine seam. Done whenmeerkat-runtime/src/runtime_loop.rsno longer owns the semantic projection logic directly. -
A-02DOGMA-08Move peer terminal context-key ownership into the chosen projection seam. Done when runtime loop no longer assembles the canonical peer terminal key itself. -
A-03DOGMA-09Movewait_allshort-circuit and barrier semantics behind lifecycle authority. Done when shell code no longer decides “all terminal already” or barrier activation semantics as the semantic owner. -
A-04DOGMA-09Move terminate-owner target scope behind lifecycle authority. Done when shell code no longer computes the authoritative non-terminal target set. -
A-05DOGMA-08DOGMA-09Add or update ownership tests for peer projection and ops lifecycle. Done when the new test coverage is ready for orchestrator execution. -
A-06DOGMA-13Unify runtime-backed turn-state authority. Done for current runtime-backed turn flows: pre-startPrimitiveAppliedand runtime dispatch no longer rely onLocalTurnExecutionStatefor authority decisions. -
A-07DOGMA-13Extend the turn-state snapshot/handle contract for runtime-backed paths. Done when runtime-backed snapshot assembly does not join handle state with a local shadow state machine. -
A-08DOGMA-13Remove runtime-backedWaitingForOpsshadow-state dependence. Done whenOpsBarrierSatisfiedand follow-up transitions use the unified authority seam only. -
A-09DOGMA-13Add or extend a defensive scan banning runtime-backed authority onLocalTurnExecutionState. Done when theA1bruntime-backed call sites are covered by the lane scan. -
A-10Self static review. Done: theA1bscan passes and the identified runtime-backed local-shadow authority sites were removed. -
A-11Handoff note. Done when handoff commit, changed files, and risks are recorded in A-plan.md. -
A-12Generated-output request. Done when any needed machine/schema/codegen follow-up is explicitly noted in the handoff, or markednone.
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.
- 4d ago First seen · 15 lines · 0 tokens per session scan A 8a49295683b1
A-checklist is an agent published in the GitHub repository lukacf/meerkat (20 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 564 tokens. 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 agents, from other repositories
generate_agent
Generates a customized agent based on user-defined parameters.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来:识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
design-reviewer
Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…