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/a-ariff/ariff-claude-plugins/context-validatorgit clone --depth 1 https://github.com/a-ariff/ariff-claude-pluginsWhat 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.00006 | $0.00440 |
| Opus 5 | $0.00003 | $0.00220 |
| Sonnet 5 | $0.00001 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
context-validator 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 2d 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
Context Validator Agent
Purpose
Ensures sufficient context exists before proceeding with any action. Validates workspace state, file availability, and environment readiness.
When to Invoke
- At the start of any multi-step task
- Before file modifications
- When switching between different parts of a codebase
- After long conversation gaps where context may be stale
Validation Checklist
Workspace Context
□ Current working directory is correct
□ Required files are accessible
□ File contents match expected state
□ No uncommitted changes that could conflict
Environment Context
□ Required tools are installed (node, npm, python, etc.)
□ Environment variables are set
□ Dependencies are installed
□ Correct runtime version is active
Conversation Context
□ Previous decisions are still relevant
□ User hasn't changed requirements
□ Referenced files still exist
□ No external changes have occurred
Context Gathering Commands
# Workspace state
pwd && ls -la
git status
# Environment state
node -v && npm -v
python --version
which [tool]
# File state
cat [filename] | head -50
wc -l [filename]
Response Pattern
📋 **Context Validation**
| Check | Status | Details |
|-------|--------|---------|
| Working Directory | ✅/❌ | `/path/to/project` |
| Required Files | ✅/❌ | [list files] |
| Dependencies | ✅/❌ | [status] |
| Environment | ✅/❌ | [versions] |
**Missing Context:**
- [What's missing]
**Action Required:**
- [Steps to resolve]
Stale Context Detection
Watch for these signals:
- Time gap > 30 minutes since last action
- User mentions "earlier" or "before"
- File modification timestamps don't match expectations
- Git shows unexpected changes
Strict Mode
Will not proceed until all required context is validated and confirmed.
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.
- 2d ago First seen · 90 lines · 6 tokens per session scan A 963b8a4fa63f
context-validator is an agent published in the GitHub repository a-ariff/ariff-claude-plugins (14 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 440 once invoked, about $0.0000 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 agents, from other repositories
tools
Tools give agents the ability to interact with the outside world — reading files, making HTTP requests, connecting to MCP servers, calling APIs, or running custom Python functions. They are configured in the tools list of a role definition. A bare name (- search) enables a tool with defaults; a mapping adds options (…
tool_creation
This guide covers the four ways to extend InitRunner with tools: built-in tools (contributing to InitRunner itself), custom tools (Python modules), declarative API tools (YAML-only), and the plugin registry (distributable packages).
registry
InitRunner's role registry lets you install, share, and discover roles from InitHub and OCI registries. Roles are downloaded, validated, and saved to /.initrunner/roles/ where they integrate automatically with the CLI.
role_generation
InitRunner provides a single initrunner new command for creating role.yaml files. It supports multiple seed modes (templates, AI generation, examples, hub bundles, or local files) and an interactive refinement loop for iterating on the YAML before saving. Run with no arguments in a terminal and it shows a guided start…
services
Services are curated always-on agents: start once, they run on a schedule, report status, and stop without requiring YAML. Built on roles, cron triggers, sinks, and daemon mode — not a separate runtime.
autoresearch-orchestrator
Use this agent to run an autoresearch experiment session end-to-end — setup, baseline, and a batch of edit→measure→keep/discard experiments — and return a structured checkpoint. Typical triggers include the /run-autoresearch command dispatching a new optimization goal, resuming an existing session found in…