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/kehanzzz/opsx-dev-workflow/agents-mdgit clone --depth 1 https://github.com/kehanzzz/opsx-dev-workflowWhat 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.00081 | $0.00081 |
| Opus 5 | $0.00041 | $0.00041 |
| Sonnet 5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
opsx-dev-workflow 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
AGENTS.md
如果当前任务已经被 opsx-development-workflow 接管，那么调用任何上游 skill 完成局部职责后，都必须回到 OpsX 主流程。
不要把上游 skill 的默认“下一步”当作整个 workflow 的最终下一步。后续动作以下一阶段定义和当前 workflow-state 的 next_action 为准。
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 · 6 lines · 81 tokens per session scan A d861cfe5ba12
opsx-dev-workflow AGENTS.md is an instructions file published in the GitHub repository kehanzzz/opsx-dev-workflow (2 stars, last pushed 4mo ago), licensed MIT. It adds 81 tokens to every session, about $0.0004 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
obsidian-agent-client AGENTS.md
AGENTS.md instructions for RAIT-09/obsidian-agent-client, covering agent client plugin - llm developer guide, architecture, data flow, acp event flow (single path) and permission flow.
three-man-team CLAUDE.md
Instructions for russelleNVy/three-man-team, covering three man team — session router, token rules — always active, session start — every role and reference files — on demand only.
xhs-imagen AGENTS.md
Instructions for NimaChu/xhs-imagen, covering repository guidance, required checks and editing rules.
memex GEMINI.md
Instructions for STiFLeR7/memex, covering memex, agent instructions, execution mode, non-negotiables and what is in scope.
kmux AGENTS.md
Instructions for kkd927/kmux, covering agents.md, kmux focus and test discipline.
obsidian-llm-hub AGENTS.md
Instructions for takeshy/obsidian-llm-hub, a project described as: Obsidian plugin for AI chat, workflow automation, and semantic search — supports Gemini, OpenAI, OpenRouter, Grok, Ollama, and CLI backends.