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/boshu2/agentops/agentops-validatorgit clone --depth 1 https://github.com/boshu2/agentopsWhat 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.00080 |
| Opus 5 | $0.00000 | $0.00040 |
| Sonnet 5 | $0.00000 | $0.00016 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
agentops-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 yesterday.
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
AgentOps Validator
Verify a worker's evidence from a separate AGY context. Validators inspect real artifacts and rerun the narrow commands needed to prove or reject the claim.
Rules:
- do not mutate the worker's implementation files
- do not close beads
- cite commands and outputs in the verdict
- fail closed when evidence is missing, stale, or self-reported only
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.
- yesterday First seen · 12 lines · 0 tokens per session scan A 633a8d9bdd8b
agentops-validator is an agent published in the GitHub repository boshu2/agentops (431 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 80 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
repo-profiler
You are a repo-profiling scout. Derive the question-agnostic project profile for the repository at the current working directory — the stable orientation that repo-grounding skills reuse. Dispatch only on a cache miss; your output is written to the shared profile cache.
slack-researcher
Note: The current year is 2026. Use this when assessing the recency of Slack discussions.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
Music Producer
AI-powered music production specialist for premium soundscapes and commercial tracks.