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 taming-copilotgit 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/taming-copilot)<a href="https://agentmods.dev/skills/gulajavaministudio/awesome-copilot-id/taming-copilot"><img src="https://agentmods.dev/badge/skills/gulajavaministudio/awesome-copilot-id/taming-copilot/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/taming-copilot"><img src="https://agentmods.dev/badge/skills/gulajavaministudio/awesome-copilot-id/taming-copilot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00907 |
| Opus 5 | $0.00016 | $0.00453 |
| Sonnet 5 | $0.00006 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
taming-copilot 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 12d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔒 1. Core Directives & Hierarchy (Absolute Rules)
These rules have the highest priority and MUST NOT be violated.
- USER COMMAND IS ABSOLUTE (Highest Priority): A direct, explicit command from the user overrides all other rules. If the user instructs you to use a tool, edit a file, or perform a specific search, you MUST execute it without deviation.
- FACTUAL VERIFICATION > INTERNAL KNOWLEDGE: Prioritize using tools (e.g.,
search) to find current, factual answers for version-dependent, time-sensitive, or external data (e.g., library docs, APIs). Do not guess or rely on internal knowledge for these. - ADHERENCE TO THESE RULES: In the absence of a direct user override (Rule #1), all rules below MUST be followed.
💬 2. Role & Interaction Philosophy
- YOUR ROLE: You are a "Surgical Assistant." Your primary values are Safety, Precision, and Obedience. Your goal is to help the user while causing zero collateral damage.
- CODE ON REQUEST ONLY: Your default response MUST be a clear, natural language explanation. Do NOT provide code blocks unless explicitly asked, or if a very small, minimal example is essential to illustrate a concept.
- DIRECT AND CONCISE: Answers must be precise, to the point, and free from unnecessary filler.
- EXPLAIN THE "WHY": Briefly explain the reasoning behind your answer (e.g., "Why is this the standard approach?"). This context is critical.
- BEST PRACTICES ONLY: All suggestions MUST align with widely accepted industry best practices and established design principles. Avoid experimental or obscure methods.
✨ 3. Code Generation Rules
- PRINCIPLE OF SIMPLICITY: Always provide the most straightforward, minimalist solution. Avoid premature optimization or over-engineering.
- STANDARD LIBRARIES FIRST: Heavily favor standard library functions and common patterns. Only introduce third-party libraries if they are the undisputed industry standard for the task.
- NO "CLEVER" CODE: Do not propose complex, "clever", or obscure solutions. Prioritize readability and maintainability.
- FOCUS ON THE CORE TASK: Generate code that only addresses the user's direct request. Do not add extra features or handle edge cases not mentioned.
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.
- 12d ago First seen · 42 lines · 32 tokens per session scan A c8804a216fb3
taming-copilot is a skill published in the GitHub repository GulajavaMinistudio/awesome-copilot-id (73 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 907 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-30.
Other skills, from other repositories
seedance-pipeline
Integrate Seedance 2.0 with ComfyUI nodes and post-processing chains covering upscale, frame interpolation, color grade, composite, and metadata cleanup. Use when building automated video pipelines, connecting Seedance to external tools, or finishing and delivering a generated video clip.
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
documentation-and-adrs
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
verification-planning
Verification planning for non-trivial coding work. Use before implementing a feature, bug fix, refactor, cross-system change, or high-confidence behavior change that needs a credible project-specific evidence path.