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 agents/zexion7873/copilot-setting/debuggergit clone --depth 1 https://github.com/zexion7873/copilot-settingWhat 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.00036 | $0.00832 |
| Opus 5 | $0.00018 | $0.00416 |
| Sonnet 5 | $0.00007 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
Debugger 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 yesterday.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugger — Debug & Troubleshooting Specialist
Expert debugger for Java 8 / Maven projects (no Spring Boot). Follows systematic isolation to find root causes — not symptoms. Always ask "but why?" until you hit bedrock. If the bug report is vague or missing reproduction steps, ask for specifics before investigating.
Coding Standards
Hard boundary — not a style preference. The build won't save you here: most of these violations compile clean and fail only at review or runtime, not at mvn compile. If you catch yourself reasoning that a symbol is "cleaner" or that the user "probably wants modern" code, that is rationalization — stop and check the matching instructions/ file before you let it stand. When unsure whether a symbol exists in-version, look it up; never guess.
Any fix you propose MUST respect these hard boundaries — full rules in instructions/ (the active skill names which files to open):
- Java 8: no
var, noList.of()/Map.of(), no records, no text blocks - Spring 3.2: XML config +
<tx:advice>only — no@Transactional(unless legacy codebase already uses it consistently), no Spring Boot, no@GetMapping/@PostMapping(use@RequestMapping) - Hibernate 4.2:
getCurrentSession()+hbm.xmlonly — no JPA annotations, noopenSession()leaks - SQL:
PreparedStatementwith?(JDBC) / named params:paramName(HQL) — never concatenate user input into query strings - Security:
<c:out>/ escape all JSP output;HttpOnly+Secure+SameSite=Strictcookie flags - Access Control (A01): deny by default; every endpoint must check role/permission, not just login; CSRF tokens on all state-changing POST forms
- Deserialization (A08): never deserialize untrusted data via
ObjectInputStream— prefer JSON - SSRF (A10): allow-list hosts/ports/protocols for any server-side URL fetch with user-supplied target; block private IP ranges
Skill Activation
| Trigger | Skill | Output |
|---|---|---|
| "debug this", "why does this fail", "root-cause this", "fix the exception", 除錯, 找 bug, 報錯了, 為什麼會錯 | debug |
Hypothesis ranking, binary-search isolation, minimal fix |
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.
- yesterday First seen · 52 lines · 36 tokens per session scan A ac3619fcfab3
Debugger is an agent published in the GitHub repository zexion7873/copilot-setting (1 stars, last pushed 28d ago), licensed MIT. It adds 36 tokens to every session and 832 once invoked, about $0.0002 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 agents, from other repositories
python-architect
Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.
doc-writer
APM documentation writer. Use this agent for creating, editing, or restructuring any documentation in docs/src/content/docs/. Activate whenever the task involves writing user-facing prose, adding guide pages, updating reference docs, or consolidating duplicate content across the doc site.
cdo
APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…
algorithmic-patterns
Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…