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/108yen/task-orchestrator-mcp/copilot-instructionsgit clone --depth 1 https://github.com/108yen/task-orchestrator-mcpWrote 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/108yen/task-orchestrator-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/108yen/task-orchestrator-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/108yen/task-orchestrator-mcp/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.1 | $0.01126 | $0.01126 |
| Opus 5 | $0.00563 | $0.00563 |
| Sonnet 5 | $0.00225 | $0.00225 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade A, and why
task-orchestrator-mcp 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 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for task-orchestrator-mcp
Documentation Structure
This project follows a structured documentation approach. For comprehensive project understanding, refer to:
Core Documentation
- Requirements:
.kiro/specs/task-management-mcp-server/requirements.md- Functional requirements and use cases - Design:
.kiro/specs/task-management-mcp-server/design.md- Architecture and system design - Tasks:
.kiro/specs/task-management-mcp-server/tasks.md- Implementation tasks and priorities
Steering Documents
- Product:
.kiro/steering/product.md- Product vision and strategy - Technical:
.kiro/steering/tech.md- Technical decisions and architecture principles - Structure:
.kiro/steering/structure.md- Project organization and conventions
Quick Reference
Core Architecture
- Entry Point:
src/index.ts→bin/index.js(CLI executable) - MCP Server:
src/server.ts- Single server instance with tool registration - Tools Layer:
src/tools.ts- Registers 7 main tools - Business Logic:
src/task.ts- Hierarchical task operations with auto-completion - Storage:
src/storage.ts- Dual-mode storage (file-based or in-memory)
Critical Workflow Pattern
The createTask tool enforces a mandatory workflow:
- Create task → 2. Call
startTask→ 3. Work → 4. CallcompleteTask→ 5. Repeat if next task assigned
Development Workflows
Refer to .kiro/steering/tech.md for detailed technical guidelines and architecture decisions.
Build System
- Primary build:
pnpm buildusestsdown(not tsc) → outputs CJS+ESM todist/ - Test runner: Vitest with V8 coverage, includes integration tests with MCP client simulation
- Quality gate:
pnpm quality= format + lint + typecheck + test (run before commits)
Git Hooks (Lefthook)
- pre-commit: Prettier (priority 1) → ESLint with auto-fix (priority 2)
- commit-msg: Commitlint validation
- post-merge: Auto
pnpm installon lockfile changes
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 · 113 lines · 1,126 tokens per session scan A d9e3e3999aeb
task-orchestrator-mcp copilot-instructions.md is an instructions file published in the GitHub repository 108yen/task-orchestrator-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 1,126 tokens to every session, about $0.0056 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).