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/dongduong2001/pudo-code-system/copilot-instructionsgit clone --depth 1 https://github.com/DongDuong2001/pudo-code-systemWrote 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/dongduong2001/pudo-code-system/copilot-instructions)<a href="https://agentmods.dev/instructions/dongduong2001/pudo-code-system/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/dongduong2001/pudo-code-system/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.00427 | $0.00427 |
| Opus 5 | $0.00214 | $0.00214 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
pudo-code-system 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 4d 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
GitHub Copilot Instructions
This repository is an AI engineering methodology and prompt/skill pack. Treat changes as documentation, workflow, and agent-instruction changes unless the task explicitly says otherwise.
PUDO Workflow
Use the PUDO loop for non-trivial work:
- Plan: define goal, scope, constraints, success criteria, and non-goals.
- Understand: inspect relevant files and existing patterns before editing.
- Develop: make small, focused patches that stay within scope.
- Optimize: self-review, run relevant checks, and summarize risks.
Use quality gates before handoff:
quality/quality-gates.mdquality/qc-checklists.mdquality/ai-output-review.mdquality/edge-cases/general.md
Repository Shape
prompts/: reusable prompt templates grouped by PUDO phase.skills/: domain and tool skills withSKILL.mdentrypoints.quality/: quality gates, QC, edge cases, and AI-output review.docs/: explanatory methodology docs.examples/: walkthroughs showing PUDO in practice.- Agent integrations live in
AGENTS.md,codex/,claude/,cursor/,opencode/,antigravity/,kiro/, and.github/.
Editing Rules
- Prefer Markdown changes that are concise, scannable, and consistent with nearby files.
- Do not rename or restructure directories unless the task requires it.
- Do not update model names or tool-specific claims unless they are verified from current docs.
- Keep legacy compatibility notes when adding newer agent config formats.
- Avoid invented commands, unsupported config keys, and broken links.
- Preserve translations unless the task explicitly asks to update them.
Verification
For docs-only changes, run the cheapest relevant checks:
git diff --check- targeted
Test-Pathchecks for new internal links - targeted
rgsearches for stale paths or deprecated wording
If checks are skipped, state why.
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.
- 4d ago First seen · 48 lines · 427 tokens per session scan A 38ce45c5ee01
pudo-code-system copilot-instructions.md is an instructions file published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 28d ago), licensed MIT. It adds 427 tokens to every session, about $0.0021 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
supergraph AGENTS.md
Instructions for datit309/supergraph, covering supergraph — mandatory workflows, skills, auto language detection, tiered workflow — pick the right tier first and full pipeline (tier 3).
agentic-coding-workflow AGENTS.md
Instructions for abhilash-m96/agentic-coding-workflow, covering agentic coding workflow, rules, step 1 — understand the full scope, step 2 — propose the chunk plan and step 3 — write the finalised plan.
docs AGENTS.md
Instructions for argos-ci/docs, covering agents.md, always use the documentation skills and keep the table of contents in sync.
PixelPilot uiux-footer.instructions.md
Footer design, links, and site information.
agent-kit CLAUDE.md
Claude Code instructions for work0r-ai/agent-kit, covering workorai-agent-kit — agent instructions, implementation protocol, preconditions (first step), 1. prior-art search (before planning) and 2. diary (.tasks/, gitignored).
PixelPilot component-storybook.instructions.md
Storybook story generation skill. Load when the user asks to "generate stories", "add Storybook", "document this component", or "create stories for". Analyses React or Vue component files, extracts props, variants, and states, and outputs production-quality .stories.tsx / .stories.ts files using the project's design…