Borrowing it
Nothing to install: this file belongs to sseshachala/conductai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sseshachala/conductai/main/.github/copilot-instructions.mdgit 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/sseshachala/conductai/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sseshachala/conductai/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00458 | $0.00458 |
| Opus 5.5 | $0.00183 | $0.00183 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (32 stars, last pushed 3d ago), licensed Apache-2.0. It adds 458 tokens to every session, about $0.0018 per session on Opus 5.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
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.