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/jonlwowski012/copilot-agent-factory/documentationgit clone --depth 1 https://github.com/jonlwowski012/copilot-agent-factoryWrote 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/jonlwowski012/copilot-agent-factory/documentation)<a href="https://agentmods.dev/instructions/jonlwowski012/copilot-agent-factory/documentation"><img src="https://agentmods.dev/badge/instructions/jonlwowski012/copilot-agent-factory/documentation.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.02022 | $0.02022 |
| Opus 5 | $0.01011 | $0.01011 |
| Sonnet 5 | $0.00404 | $0.00404 |
| Haiku 4.5 | $0.00202 | $0.00202 |
Grade A, and why
copilot-agent-factory documentation.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.
How it starts
The opening of the file, as written. The whole thing — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Instructions
Domain: Markdown Documentation (README, guides, examples)
Applies To: README.md, docs/MCP-SERVERS.md, planning artifacts, examples
Documentation Standards
Keep It Concise
- README.md: Target 900 lines, max 1000 lines
- Other docs: As long as needed, but favor clarity over verbosity
- Examples: Short, focused, working code
Examples First
Always show concrete examples before explaining theory:
❌ Don't do this:
## Placeholder System
The placeholder system uses a template-based approach with variable substitution
enabling dynamic content generation through marker replacement...
✅ Do this instead:
## Placeholder System
Templates use `{{placeholder}}` markers that get replaced:
```markdown
**Tech Stack:** {{tech_stack}}
Becomes:
**Tech Stack:** Python 3.10, FastAPI, PyTorch
### Structure for Readability
Use tables, lists, and headings effectively:
**For comparisons:**
| Aspect | Agents | Skills |
|--------|--------|--------|
| Purpose | Role-based experts | Workflow procedures |
| Invocation | `@agent-name` | Auto-activates |
**For steps:**
1. First step
2. Second step
3. Third step
**For categories:**
- **Category 1:** Items with bold labels
- **Category 2:** Items with bold labels
## README.md Structure
Maintain this structure in README.md:
1. **Title & Tagline**
2. **What is this?** (quick overview with bullets)
3. **Quick Start** (3 steps)
4. **Agents vs Skills** (comparison table)
5. **MCP Server Auto-Detection**
6. **Global Instruction Files**
7. **Feature Development Workflow**
8. **Directory Structure**
9. **Available Agent Templates** (46 total)
10. **Available Skills** (7 total)
11. **MCP Server Integrations**
12. **Detection Rules**
13. **Template Placeholders**
14. **Customization**
15. **Best Practices**
16. **Agent Capabilities**
17. **Example Generated Output**
18. **Contributing**
19. **References**
### Updating Sections
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 · 387 lines · 2,022 tokens per session scan A 4328c0797ce0
copilot-agent-factory documentation.instructions.md is an instructions file published in the GitHub repository jonlwowski012/copilot-agent-factory (16 stars, last pushed 4mo ago), licensed MIT. It adds 2,022 tokens to every session, about $0.0101 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
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.