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/sseshachala/conductai/copilot-instructionsgit clone --depth 1 https://github.com/sseshachala/conductaiWrote 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/sseshachala/conductai/copilot-instructions)<a href="https://agentmods.dev/instructions/sseshachala/conductai/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sseshachala/conductai/copilot-instructions.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.00458 | $0.00458 |
| Opus 5 | $0.00229 | $0.00229 |
| Sonnet 5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
conductai copilot-instructions.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 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.
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
ConductGuard Policy
At the start of every conversation:
- Call
guard_activityONCE with a one-line summary of what the user is asking.
Then, for the request itself:
- Call
guard_checkONCE per intent — not per file, per command, or per edit. - Re-check only when scope changes (reads → writes, local → network, or a new task).
- If BLOCKED: stop and explain the policy rule to the user.
- If WARNING: proceed but surface the warning inline.
- If the response is
okor empty: proceed silently. Do NOT narrate it in the chat.
Example:
- User asks to fix a bug → call
guard_activityonce with the summary. - Before starting the code changes → call
guard_checkonce with the intent (e.g.write_file,bash). - Do NOT re-check for every subsequent read or edit in the same task.
Never write secrets to files or output. Never send PII to external endpoints.
ConductGuard Policy
At the start of every conversation:
- Call
guard_activityONCE with a one-line summary of what the user is asking.
Then, for the request itself:
- Call
guard_checkONCE per intent — not per file, per command, or per edit. - Re-check only when scope changes (reads → writes, local → network, or a new task).
- If BLOCKED: stop and explain the policy rule to the user.
- If WARNING: proceed but surface the warning inline.
- If the response is
okor empty: proceed silently. Do NOT narrate it in the chat.
Example:
- User asks to fix a bug → call
guard_activityonce with the summary. - Before starting the code changes → call
guard_checkonce with the intent (e.g.write_file,bash). - Do NOT re-check for every subsequent read or edit in the same task.
Never write secrets to files or output. Never send PII to external endpoints.
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 · 40 lines · 458 tokens per session scan A 6a9369056146
conductai copilot-instructions.md is an instructions file published in the GitHub repository sseshachala/conductai (24 stars, last pushed 4d ago), licensed Apache-2.0. It adds 458 tokens to every session, about $0.0023 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 instructions, from other repositories
full-stack-ai-agent-template CLAUDE.md
Instructions for vstorm-co/full-stack-ai-agent-template, covering claude.md, project overview, commands, install dependencies and run tests.
full-stack-ai-agent-template AGENTS.md
Instructions for vstorm-co/full-stack-ai-agent-template, covering agents.md, project overview, commands, cli and architecture.
tracecat AGENTS.md
AGENTS.md instructions for TracecatHQ/tracecat, covering tracecat agent notes, path-specific notes, repo map, fargate deployment notes and setup and verification.
tracecat CLAUDE.md
Claude Code instructions for TracecatHQ/tracecat, a project described as: Open-source security automation platform for teams and AI agents.
e-commerce-agents CLAUDE.md
Instructions for nitin27may/e-commerce-agents, covering claude.md, what this is, working artifacts location, key commands and start everything from scratch (one command).
OpenNotebookLM AGENTS.md
Instructions for tom1030507/OpenNotebookLM, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.