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 skills/grimoire-rs/grimoire/meta-validate-contextnpx skills add grimoire-rs/grimoire --skill meta-validate-contextgit clone --depth 1 https://github.com/grimoire-rs/grimoireWrote 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/grimoire-rs/grimoire/meta-validate-context)<a href="https://agentmods.dev/skills/grimoire-rs/grimoire/meta-validate-context"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/meta-validate-context.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.00038 | $0.00523 |
| Opus 5 | $0.00019 | $0.00262 |
| Sonnet 5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
meta-validate-context 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 5d 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
Validate Context Rules
Check .claude/rules/subsystem-*.md files match current codebase.
Workflow
For each subsystem-*.md rule file:
- Read the rule — Extract type names, module paths, function names, error variants
- Grep the codebase — Verify each reference exists
- Check for new additions — Find new public types/modules not in rule
- Report — List stale references + missing additions
Subsystem Rules to Check
| Rule | Key References to Verify |
|---|---|
subsystem-cli.md |
CLI context struct, command enum variants, output trait |
subsystem-cli-api.md |
Report data types, output trait conventions |
subsystem-cli-commands.md |
Documented command surface vs implemented commands |
subsystem-file-structure.md |
Storage layout, data-root constraints |
subsystem-tests.md |
Fixture names in conftest.py, test file names, runner methods, helper params |
Subsystem rules are provisional placeholders while the implementation is
scaffolded — verify against current src/ as code lands.
Verification Commands
# Check if a type still exists
grep -r "pub struct TypeName" src/
grep -r "pub enum TypeName" src/
# Check if a module still exists
ls src/module_name/
# Check for new public types not in the rule
grep -rn "^pub struct\|^pub enum\|^pub trait" src/ | grep -v test
Output Format
## Context Validation Report
### subsystem-cli.md
- OK: [type] still present
- STALE: [type] — renamed to [new_name] or removed
- MISSING: [new_type] — not documented in rule
### subsystem-file-structure.md
...
When to Run
- After big refactors
- Before major feature branches
- Part of
/code-checkaudits - Monthly
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.
- 5d ago First seen · 72 lines · 38 tokens per session scan A d20f6ac677ac
meta-validate-context is a skill published in the GitHub repository grimoire-rs/grimoire (8 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 523 once invoked, about $0.0002 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 skills, from other repositories
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
haiku
When writing a haiku for this bot, follow these conventions.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.