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 instructions/rzfl/agentops-mcp/agents-mdgit clone --depth 1 https://github.com/RZFL/agentops-mcpWhat 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.00271 | $0.00271 |
| Opus 5 | $0.00135 | $0.00135 |
| Sonnet 5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
agentops-mcp AGENTS.md 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
Agent Guidelines
Project Purpose
AgentOps Guardian MCP is a local-first MCP safety agent for AI coding workflows. It helps developers review risky actions, create file checkpoints, and roll back workflow changes when an agent makes an unsafe edit.
Core Capabilities
guardian_run_workflow: inspect an action, score risk, create checkpoints when needed, and return a structured decision.guardian_restore_workflow: restore every file checkpointed by a saved workflow.safe_checkpointandrestore_latest: lightweight file-level rollback helpers.inspect_agent_environment_componentsandscore_agent_surface: deterministic inspection of local agent/MCP/tooling configuration.
Development Rules
- Keep the project local-first and deterministic.
- Prefer small TypeScript modules with explicit
try/catcherror handling. - Return MCP tool errors inside structured tool output instead of uncaught process exceptions.
- Require explicit user approval before destructive shell commands, publishing, or release actions.
- Do not commit credentials, API keys, local
.envfiles, generated build output, or local workflow state. - Keep public documentation focused on the product, demo flow, and reproducible setup.
Verification
Before final submission, run:
npm install
npm run check
npm test
npm run build
npm run demo:workflow
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 · 34 lines · 271 tokens per session scan A 1adb78fbc959
agentops-mcp AGENTS.md is an instructions file published in the GitHub repository RZFL/agentops-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 271 tokens to every session, about $0.0014 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.