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/ourobx/agent-ebpf/doc-coauthoringgit clone --depth 1 https://github.com/ourobx/agent-ebpfWrote 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/instructions/ourobx/agent-ebpf/doc-coauthoring)<a href="https://agentmods.dev/instructions/ourobx/agent-ebpf/doc-coauthoring"><img src="https://agentmods.dev/badge/instructions/ourobx/agent-ebpf/doc-coauthoring.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.03331 | $0.03331 |
| Opus 5 | $0.01665 | $0.01665 |
| Sonnet 5 | $0.00666 | $0.00666 |
| Haiku 4.5 | $0.00333 | $0.00333 |
Grade C, and why
agent-ebpf doc-coauthoring.instructions.md scanned grade C with 1 finding 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 3d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Copilot Instruction Telemetry: This file was auto-generated by Claude Skills Manager --> How it starts
The opening of the file, as written. The whole thing — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-coauthoring
Doc Co-Authoring Workflow
This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.
When to Offer This Workflow
Trigger conditions:
- User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up"
- User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC"
- User seems to be starting a substantial writing task
Initial offer: Offer the user a structured workflow for co-authoring the document. Explain the three stages:
- Context Gathering: User provides all relevant context while Claude asks clarifying questions
- Refinement & Structure: Iteratively build each section through brainstorming and editing
- Reader Testing: Test the doc with a fresh Claude (no context) to catch blind spots before others read it
Explain that this approach helps ensure the doc works well when others read it (including when they paste it into Claude). Ask if they want to try this workflow or prefer to work freeform.
If user declines, work freeform. If user accepts, proceed to Stage 1.
Stage 1: Context Gathering
Goal: Close the gap between what the user knows and what Claude knows, enabling smart guidance later.
Initial Questions
Start by asking the user for meta-context about the document:
- What type of document is this? (e.g., technical spec, decision doc, proposal)
- Who's the primary audience?
- What's the desired impact when someone reads this?
- Is there a template or specific format to follow?
- Any other constraints or context to know?
Inform them they can answer in shorthand or dump information however works best for them.
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.
- 3d ago First seen · 385 lines · 3,331 tokens per session scan C e7d2367cd314
agent-ebpf doc-coauthoring.instructions.md is an instructions file published in the GitHub repository ourobx/agent-ebpf (1 stars, last pushed 9d ago), licensed MIT. It adds 3,331 tokens to every session, about $0.0167 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
casbin-gateway CLAUDE.md
Claude Code instructions for apache/casbin-gateway, covering claude.md and code style.
aigis CLAUDE.md
Claude Code instructions for killertcell428/aigis, covering aigis — project guidelines, zenn記事管理（zenn cli + github連携）, ディレクトリ構成, 記事の作成 and プレビュー.
preloop AGENTS.md
AGENTS.md instructions for preloop/preloop, covering preloop development guide, commands, git workflow, keep sample data generic and code style.
pfsense-mcp-server AGENTS.md
AGENTS.md instructions for night4me/pfsense-mcp-server, covering pfsense mcp server, architecture and security, development workflow, long-running validation and test parallelism.
xops-cli AGENTS.md
AGENTS.md instructions for wentf9/xops-cli, covering ai 助手开发协作指南 (agents.md), 🎨 1. 编码规范 (coding standards), 📦 2. git 规范 (git standards) and 🛠️ 3. 测试、构建与 ci (testing, building & ci).
fwskillsshare AGENTS.md
Instructions for fastrevmd-lab/fwskillsshare, covering firewall skills repository instructions, purpose and architecture, setup and development, required checks and skill description constraints.