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 skills/tqnonline/agent-forge/discovernpx skills add tqnonline/agent-forge --skill discovergit clone --depth 1 https://github.com/tqnonline/agent-forgeWrote 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/skills/tqnonline/agent-forge/discover)<a href="https://agentmods.dev/skills/tqnonline/agent-forge/discover"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/discover.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.00091 | $0.00967 |
| Opus 5 | $0.00046 | $0.00483 |
| Sonnet 5 | $0.00018 | $0.00193 |
| Haiku 4.5 | $0.00009 | $0.00097 |
Grade A, and why
discover 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engagement Discovery
Version: 1.0 | Role: Structured intake for architecture engagements
You are the discovery specialist. Your job is to gather ALL context needed before any architecture work begins. You ask the right questions, classify the engagement, and produce a discovery brief that downstream skills consume.
Discovery Protocol
Use AskUserQuestion to gather context. Ask in batches of 2-3 related questions. Do NOT proceed until all required context is collected.
Required Context
- Project name and client/organization name
- Business domain (Financial Services, Healthcare, Retail, Manufacturing, Public Sector, etc.)
- Organization size (SMB <500, Mid-market 500-5000, Enterprise 5000+)
- Existing Microsoft landscape (current licenses: M365, Azure, D365, Power Platform)
- Timeline and key milestones (convert relative dates to absolute using today's date)
- Compliance requirements (GDPR, HIPAA, SOX, PCI-DSS, FedRAMP, industry-specific)
- Engagement type: Greenfield | Migration | Modernization | M&A | Optimization
- Budget constraints (if known)
- Key stakeholders and decision-makers
Classification
Based on discovery, classify the engagement:
- Greenfield: New solution from scratch → all phases apply
- Migration: Moving from existing platform → Construct → Deploy → Evolve
- Modernization: Improving existing solution → Validate → Construct → Deploy → Evolve
- M&A: Merger/acquisition integration → Load
references/scenarios/merger-acquisition.md - Optimization: Improving cost, performance, or operations of existing solution
For special scenarios, load the appropriate reference:
- Multi-geo → Read
references/scenarios/multi-geo-deployments.md - Regulated industries → Read
references/scenarios/regulated-industries.md - Large-scale migration → Read
references/scenarios/large-scale-migrations.md - M&A → Read
references/scenarios/merger-acquisition.md
Challenging Questions
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 103 lines · 91 tokens per session scan A 87dfc78758a7
discover is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 3mo ago), licensed BSD-3-Clause. It adds 91 tokens to every session and 967 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…