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/charannyk06/conductor-oss/agents-mdgit clone --depth 1 https://github.com/charannyk06/conductor-ossWrote 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/charannyk06/conductor-oss/agents-md)<a href="https://agentmods.dev/instructions/charannyk06/conductor-oss/agents-md"><img src="https://agentmods.dev/badge/instructions/charannyk06/conductor-oss/agents-md.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.00842 | $0.00842 |
| Opus 5 | $0.00421 | $0.00421 |
| Sonnet 5 | $0.00168 | $0.00168 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
conductor-oss 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI agents contributing to Conductor OSS.
Project Overview
Conductor OSS is a local-first AI agent orchestrator built with Rust + Next.js. It dispatches coding tasks from Markdown kanban boards to agent CLIs, running them in isolated worktrees with live dashboard streaming.
Before You Start
- Read
CLAUDE.mdfor architecture and conventions - Run
cargo test --workspaceto verify the build - Check
CONDUCTOR-TAGS.mdfor task tagging conventions - Branch from
main, use conventional commit messages
Code Style
Rust (primary codebase)
- Error handling:
thiserrorfor library errors,anyhowfor binaries - Async: tokio runtime, axum for HTTP
- Database: sqlx with SQLite, migrations in
conductor-db - State:
Arc<RwLock<T>>orDashMapfor concurrent access - Tests: inline
#[cfg(test)]modules plus crate and workspace integration tests - No
unwrap()in library code; use?or explicit error handling
TypeScript (dashboard + CLI launcher)
- Runtime: Bun >= 1.2
- Framework: Next.js 16, App Router
- No default exports in library code
- ESM only
PR Checklist
-
cargo test --workspacepasses -
cargo clippy --workspacehas no warnings -
bun run typecheckpasses (if TS changes) - PR has
## Type of Changesection with checkboxes - PR has
## User-Facing Release Noteswith plain-English bullets
Key Directories
crates/
conductor-core/ # Types, config, board parsing, task models
conductor-server/ # HTTP server, routes, state, SSE
conductor-db/ # SQLite persistence
conductor-executors/ # Agent adapters, process management
conductor-git/ # Git operations
conductor-relay/ # Relay server for bridge and remote terminal flows
conductor-watcher/ # File system watching
conductor-cli/ # Rust CLI
conductor-types/ # Shared bridge/transport protocol types
notify-rust/ # Desktop notification support
bridge-cmd/ # Companion bridge binary used by paired-device flows
packages/
cli/ # npm CLI launcher
core/ # Shared TS types (being superseded by Rust)
web/ # Next.js dashboard
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.
- 5d ago First seen · 91 lines · 842 tokens per session scan A dba47eb7cc64
conductor-oss AGENTS.md is an instructions file published in the GitHub repository charannyk06/conductor-oss (49 stars, last pushed 2d ago), licensed Apache-2.0. It adds 842 tokens to every session, about $0.0042 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
coding-wrapped AGENTS.md
Instructions for senlindesign/coding-wrapped, a project described as: A local-first Coding Wrapped Skill for Claude Code and Codex.
Vibe-Research AGENTS.md
AGENTS.md instructions for simonlin1212/Vibe-Research, covering vibe-research-agent 金融研究宪法, 0. 三条不可越线, 1. 数据纪律(五问 gate:给出任何数字或结论前逐条自问), 2. 研究哲学(评估框架,不是预测工具) and 3. 估值口径(你只选输入、解释输出;计算交给 calc/).
ephemeral-sandbox CLAUDE.md
Instructions for Ephemeral-AI-Lab/ephemeral-sandbox, covering claude.md, project, engineering practice (required), build & test and sandbox tools.
coral CLAUDE.md
Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).
pixir CLAUDE.md
Instructions for Ranvier-Technologies/pixir, covering pixir harness - legacy agent guide, current map and commands.
Agent-Memory-Bridge AGENTS.md
Instructions for zzhang82/Agent-Memory-Bridge, covering agent memory bridge contributor instructions, setup and checks, architecture boundaries, mutation and migration invariants and benchmark expectations.