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 ABilenduke/copilot-developer --skill featuregit clone --depth 1 https://github.com/ABilenduke/copilot-developerWrote 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/abilenduke/copilot-developer/feature)<a href="https://agentmods.dev/skills/abilenduke/copilot-developer/feature"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/feature/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/abilenduke/copilot-developer/feature"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/feature.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.00083 | $0.02469 |
| Opus 5.5 | $0.00033 | $0.00988 |
| Sonnet 5.5 | $0.00017 | $0.00494 |
| Haiku 4.5 | $0.00008 | $0.00247 |
Grade A, and why
feature 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 1mo 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Discovery Skill
Purpose
This skill builds and maintains a living catalog of application features in docs/features/. Through interactive Q&A, it helps the developer articulate what each feature is and why it exists, creating lightweight documentation that serves as the organizational backbone for planning and execution.
First Steps
When this skill is invoked:
- Read the supporting files in this skill directory:
templates/feature-readme-v2.md— template for individual feature READMEs (Diátaxis structure: Overview, Architecture, Common Tasks, Stories)templates/feature-readme.md— legacy template (for reference only; use v2 for all new features)templates/index.md— template for the feature catalog index
- Check if
docs/features/already exists:- If yes: Read
docs/features/index.mdand list existing features. Ask the user what they want to do (add a new feature, update an existing one, review the catalog). - If no: This is a fresh start. Explain briefly what you're building, then begin discovery.
- If yes: Read
- Explore the codebase to understand what exists (routes, controllers, models, directories) — this gives you informed suggestions during discovery.
Modes of Operation
Mode 1: Initial Discovery (Fresh Catalog)
Walk the developer through mapping out their entire application. This is a brainstorming conversation.
Approach:
- Explore the codebase first (directory structure, routes, models, key config files)
- Propose an initial list of features based on what you find: "Based on the codebase, I can see what looks like: auth, billing, notifications, reporting, and an admin panel. Does that sound right? What am I missing?"
- For each feature, have a brief conversation to nail down:
- What is it? (1-3 sentence description)
- Why does it exist? (What problem does it solve?)
- Create the directory structure and files (each feature gets:
README.md,stories/,bugs/,spikes/) - Generate the index
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.
- 1mo ago First seen · 212 lines · 83 tokens per session scan A d5a956c3d03c
feature is a skill published in the GitHub repository ABilenduke/copilot-developer (4 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 2,469 once invoked, about $0.0003 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…