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/eg-plangit 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/eg-plan)<a href="https://agentmods.dev/agents/lukacf/meerkat/eg-plan"><img src="https://agentmods.dev/badge/agents/lukacf/meerkat/eg-plan.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.01739 |
| Opus 5 | $0.00000 | $0.00870 |
| Sonnet 5 | $0.00000 | $0.00348 |
| Haiku 4.5 | $0.00000 | $0.00174 |
Grade A, and why
EG-plan 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lane EG Plan
Owned Rows
DOGMA-14DOGMA-18DOGMA-20DOGMA-23
Owned Milestones
EG1a=DOGMA-20EG1b=DOGMA-14,DOGMA-23EG2=DOGMA-18
Owned Files
meerkat-session/src/persistent.rsmeerkat-core/src/session_recovery.rsmeerkat/src/surface/runtime_backed.rsmeerkat-mob/src/runtime/builder.rsmeerkat-mob/src/runtime/session_service.rsmeerkat-rpc/src/realtime_ws.rsmeerkat/src/surface/schedule_host.rsmeerkat-skills/src/resolve.rs
Shared Files Touched Under Round Map
meerkat-rpc/src/realtime_ws.rsas first owner forEG1ameerkat-rest/src/lib.rsas second owner only forEG2, afterB1meerkat-rpc/src/session_runtime.rsas second owner only forEG2, afterB1meerkat-rpc/src/handlers/session.rsas second owner only forEG2, afterB1
Blocked By
EG2blocked byB1
Unblocks
B2afterEG1a
Public / Type / Schema Changes
DOGMA-20changes websocket/product-session behavior, not public namingDOGMA-23is a full schedule-domain typed outcome fix and may require schema freshness workDOGMA-18changes canonical default skill-source identity resolution
Defensive Scan Commitments
- add or update a scan banning helper-local UUID fabrication for default skill sources outside the canonical registry path
Requested Orchestrator Probes
./scripts/repo-cargo check -p meerkat-rpc./scripts/repo-cargo check -p meerkat-mob./scripts/repo-cargo check -p meerkat-session./scripts/repo-cargo check -p meerkat-core./scripts/repo-cargo check -p meerkat-schedule./scripts/repo-cargo check -p meerkat./scripts/repo-cargo check -p meerkat-skills./scripts/repo-cargo check -p meerkat-rest- if schedule/public artifacts change:
make regen-schemasmake verify-schema-freshness
Requested Build Gate Commands
- Quick probe
EG1a:./scripts/repo-cargo check -p meerkat-rpc./scripts/repo-cargo check -p meerkat-mob
- Quick probe
EG1b:./scripts/repo-cargo check -p meerkat-session./scripts/repo-cargo check -p meerkat-core./scripts/repo-cargo check -p meerkat-schedule./scripts/repo-cargo check -p meerkatmake regen-schemasmake verify-schema-freshness
- Quick probe
EG2:./scripts/repo-cargo check -p meerkat-skills./scripts/repo-cargo check -p meerkat-rpc./scripts/repo-cargo check -p meerkat-rest
- Full gate
EG1a:./scripts/repo-cargo nextest run -p meerkat-rpc --lib --show-progress none --status-level none --final-status-level fail./scripts/repo-cargo nextest run -p meerkat-rpc --test realtime_ws_protocol --show-progress none --status-level none --final-status-level fail./scripts/repo-cargo nextest run -p meerkat-mob --test member_realtime_bindings --show-progress none --status-level none --final-status-level fail./scripts/repo-cargo e2e-fast
- Full gate
EG1b:./scripts/repo-cargo nextest run -p meerkat-session --lib --show-progress none --status-level none --final-status-level fail./scripts/repo-cargo nextest run -p meerkat-session --test regression_lifecycle --show-progress none --status-level none --final-status-level fail./scripts/repo-cargo nextest run -p meerkat-schedule --lib --show-progress none --status-level none --final-status-level fail./scripts/repo-cargo nextest run -p meerkat --lib --show-progress none --status-level none --final-status-level fail./scripts/repo-cargo e2e-fast
- Full gate
EG2:./scripts/repo-cargo nextest run -p meerkat-skills --lib --show-progress none --status-level none --final-status-level fail./scripts/repo-cargo nextest run -p meerkat-core --test skill_identity_migrations --show-progress none --status-level none --final-status-level fail./scripts/repo-cargo nextest run -p meerkat-rpc --lib --show-progress none --status-level none --final-status-level fail./scripts/repo-cargo nextest run -p meerkat-rest --lib --show-progress none --status-level none --final-status-level fail./scripts/repo-cargo e2e-fast
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 · 136 lines · 0 tokens per session scan A df61c4439352
EG-plan 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 1,739 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…