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 euxx/claude-skills-for-copilot --skill feature-devgit clone --depth 1 https://github.com/euxx/claude-skills-for-copilotWrote 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/euxx/claude-skills-for-copilot/feature-dev)<a href="https://agentmods.dev/skills/euxx/claude-skills-for-copilot/feature-dev"><img src="https://agentmods.dev/badge/skills/euxx/claude-skills-for-copilot/feature-dev/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/euxx/claude-skills-for-copilot/feature-dev"><img src="https://agentmods.dev/badge/skills/euxx/claude-skills-for-copilot/feature-dev.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.00033 | $0.01940 |
| Opus 5.5 | $0.00013 | $0.00776 |
| Sonnet 5.5 | $0.00007 | $0.00388 |
| Haiku 4.5 | $0.00003 | $0.00194 |
Grade A, and why
feature-dev 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Development
You are helping a developer implement a new feature. Follow a systematic approach: understand the codebase deeply, identify and ask about all underspecified details, design elegant architectures, then implement.
Core Principles
- Ask clarifying questions: Identify all ambiguities, edge cases, and underspecified behaviors. Ask specific, concrete questions rather than making assumptions. Wait for user answers before proceeding. Ask questions early — after understanding the codebase, before designing.
- Understand before acting: Read and comprehend existing code patterns first.
- Read files identified by agents: When launching agents, ask them to return lists of the most important files to read. After agents complete, read those files to build detailed context before proceeding.
- Simple and elegant: Prioritize readable, maintainable, architecturally sound code.
- Use a todo list: Track all progress throughout.
Phase 1: Discovery
Goal: Understand what needs to be built.
Initial request: $ARGUMENTS
Actions:
- Create a todo list with all phases.
- If the feature is unclear, ask the user:
- What problem are they solving?
- What should the feature do?
- Any constraints or requirements?
- Summarize understanding and confirm with user.
Phase 2: Codebase Exploration
Goal: Understand relevant existing code and patterns at both high and low levels.
Actions:
-
Launch 2–3 code-explorer sub-agents in parallel. Each agent should:
- Trace through the code comprehensively, focusing on abstractions, architecture, and flow of control.
- Target a different aspect of the codebase (e.g. similar features, high-level architecture, user experience, testing patterns).
- Return a list of 5–10 key files to read.
Example prompts:
- "Find features similar to [feature] and trace through their implementation comprehensively"
- "Map the architecture and abstractions for [feature area], tracing through the code comprehensively"
- "Analyze the current implementation of [existing feature/area], tracing through the code comprehensively"
- "Identify UI patterns, testing approaches, or extension points relevant to [feature]"
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 · 196 lines · 33 tokens per session scan A 40a758ce5904
feature-dev is a skill published in the GitHub repository euxx/claude-skills-for-copilot (4 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 1,940 once invoked, about $0.0001 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
jetbrains-ui
Use when writing or reviewing UI code in packages/kilo-jetbrains/ — Swing layout, platform components, UiStyle tokens, theme colors/fonts/borders, Stack/Align layouts, tool windows/dialogs/popups/notifications, settings pages, and the pre-return UI checklist.
jetbrains-arch
Use when adding or moving code across shared/frontend/backend modules in packages/kilo-jetbrains/ — split-mode RPC contracts, serialization classloader pitfall, threading/EDT annotations, services and coroutine scopes, EDT test rules, dependency bundling, and the CLI server protocol.
jetbrains-session
Use when working on the JetBrains chat session UI or SessionModel/SessionController — transcript cards, retained Swing lifecycle, session background surfaces, editor-derived styling, adding session events, and session/controller testing with FakeSessionRpcApi.
icon-jetbrains
Create or review IntelliJ New UI SVG icons, theme variants, sizes, and palette.
vscode-visual-regression
Write Storybook stories and visual regression tests for the Kilo VS Code extension webview UI.
pr-track-v1
Create a GitHub tracking issue in Kilo-Org/kilocode that captures a merged Kilo v1 PR's behavior so it can be re-implemented or verified in opencode v2. Use when the user invokes /pr-track-v1 or asks to track a v1 core fix/feature for the v2 rewrite.