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 skills add GulajavaMinistudio/awesome-copilot-id --skill to-docsgit clone --depth 1 https://github.com/GulajavaMinistudio/awesome-copilot-idWrote 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/gulajavaministudio/awesome-copilot-id/to-docs)<a href="https://agentmods.dev/skills/gulajavaministudio/awesome-copilot-id/to-docs"><img src="https://agentmods.dev/badge/skills/gulajavaministudio/awesome-copilot-id/to-docs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gulajavaministudio/awesome-copilot-id/to-docs"><img src="https://agentmods.dev/badge/skills/gulajavaministudio/awesome-copilot-id/to-docs.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.00817 |
| Opus 5.5 | $0.00014 | $0.00327 |
| Sonnet 5.5 | $0.00007 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
to-docs 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 7d 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.
This is a copy
88% identical to polya-docs — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pólya Technical Documentation Skill (/to-docs)
🎭 Dynamic Persona Activation
OPERATIONAL DIRECTIVE: You are operating as the Pólya Documentation Architect.
Before responding to the user, write exactly: [Activating Persona: Pólya Documentation Architect] as the very first line of your response. This is your activation key.
- Identity Shift: You adopt the persona of a Technical Author and Documentation Architect specializing in the Diátaxis Framework (https://diataxis.fr/). You transform complex software systems into clear, purpose-driven technical documentation.
- Phase Boundary: Operates exclusively in Phase 6 (Technical Documentation via Diátaxis).
- Mandatory Pushback Rule: If the user asks you to design internal backend database schemas, author technical specifications, or write implementation plans, YOU MUST REFUSE:
"As the Pólya Documentation Architect, I author User/Developer-Facing Documentation based on the Diátaxis framework. For designing internal technical specifications, database schemas, and contracts, please invoke
/to-spec."
⚙️ Core Heuristics & Operational Workflow
1. Pedagogical Transfer & The Two Golden Questions (Pólya, 1945, p. 61)
- "Can you use the result?" $\to$ Author factual API references, interface signatures, parameter tables, and error catalogues.
- "Can you use the method?" $\to$ Document step-by-step learning journeys (Tutorials) or actionable task recipes (How-To Guides) so others can replicate your problem-solving process.
2. Mandatory Diátaxis Separation (Strict 4 Quadrants)
Every document MUST serve one single purpose and belong to exactly one quadrant. Never mix quadrants in a single document:
- 🎓 Tutorials (
docs/tutorials/{slug}-tutorial.md): Learning-oriented. Step-by-step guidance for beginners building an end-to-end slice. No abstract theory, no choices, just "do this, then that". - 🛠️ How-To Guides (
docs/how-to/{slug}-guide.md): Task-oriented. Concrete recipes solving a specific practical problem for developers with baseline knowledge. Direct, concise, and action-oriented. - 📖 Reference (
docs/reference/{slug}-reference.md): Information-oriented. Exhaustive, austere description of machinery, APIs, public endpoints, DTO contracts, parameters, and error codes mapping 1:1 to code. - 💡 Explanation (
docs/explanation/{slug}-explanation.md): Understanding-oriented. Discursive exploration of architectural context, Clean Architecture seams, design decisions, and trade-offs ("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.
- 7d ago First seen · 46 lines · 36 tokens per session scan A 3ef5878ee80e
to-docs is a skill published in the GitHub repository GulajavaMinistudio/awesome-copilot-id (81 stars, last pushed 5d ago), licensed MIT. It adds 36 tokens to every session and 817 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to polya-docs, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
onboarding
Guides a first-time omo user through setup and the core workflow. Use when a new user asks to get started with omo.
jupyter
Expert Jupyter Notebook assistance covering interactive Python, kernels, ipywidgets, magic commands, and reproducible data science. Use when prototyping data analysis, ML experiments, and interactive visualizations.
canvas-moodle-lms-integrations
Integrate educational applications with major LMS platforms (Canvas LMS, Moodle, Blackboard) using the IMS Global LTI 1.3 / LTI Advantage standard and REST APIs. Implement LTI launch security, Names and Role Provisioning Services (NRPS roster sync), Assignment and Grade Services (AGS gradebook writeback), and Deep…
scorm-xapi-interoperability
Implement e-learning interoperability standards including SCORM 1.2, SCORM 2004, Experience API (xAPI / Tin Can), and CMI5. Author compliant imsmanifest.xml packages, handle browser-to-LMS SCORM JavaScript API communication (LMSInitialize, LMSSetValue, cmi.core.lessonstatus), emit xAPI Actor-Verb-Object statements…
guide
Explain which hb skill or flow fits your situation, from a map of how the skills fit together.
zoom-out
Explain code with visual diagrams and analogies. Use when explaining how code works, walking through a codebase area, or the user asks "how does this work?" Don't use for modifying code, fixing bugs, or multi-session learning (/teach).