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 conventions-improvergit 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/conventions-improver)<a href="https://agentmods.dev/skills/euxx/claude-skills-for-copilot/conventions-improver"><img src="https://agentmods.dev/badge/skills/euxx/claude-skills-for-copilot/conventions-improver/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/conventions-improver"><img src="https://agentmods.dev/badge/skills/euxx/claude-skills-for-copilot/conventions-improver.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.00072 | $0.01566 |
| Opus 5.5 | $0.00029 | $0.00626 |
| Sonnet 5.5 | $0.00014 | $0.00313 |
| Haiku 4.5 | $0.00007 | $0.00157 |
Grade A, and why
conventions-improver 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.
Conventions File Improver
Audit, evaluate, and improve project conventions files (AGENTS.md, CLAUDE.md, GEMINI.md) to ensure AI agents have optimal project context.
This skill can write to conventions files. After presenting a quality report and getting user approval, it applies targeted improvements.
Workflow
Phase 1: Discovery
Find all conventions files in the repository using this priority order: AGENTS.md, then CLAUDE.md, then GEMINI.md.
Search for files named AGENTS.md, CLAUDE.md, or GEMINI.md at the root and in any subdirectories.
File Types & Locations:
| Type | Location | Purpose |
|---|---|---|
| Project root | ./AGENTS.md (or CLAUDE.md, GEMINI.md) |
Primary project context, shared with team |
| Package-specific | ./packages/*/AGENTS.md |
Module-level context in monorepos |
| Subdirectory | Any nested location | Feature/domain-specific context |
Note: AI agents auto-discover conventions files in parent directories, so monorepo setups work automatically.
Phase 2: Quality Assessment
For each conventions file found, evaluate it against the following scoring rubric (total: 100 points):
Scoring Criteria
1. Commands/Workflows (20 points)
- 20: All essential commands documented with context (build, test, lint, deploy, dev)
- 15: Most commands present, some missing context
- 10: Basic commands only, no workflow
- 5: Few commands, many missing
- 0: No commands documented
2. Architecture Clarity (20 points)
- 20: Clear codebase map — key directories explained, module relationships, entry points, data flow
- 15: Good structure overview, minor gaps
- 10: Basic directory listing only
- 5: Vague or incomplete
- 0: No architecture info
3. Non-Obvious Patterns (15 points)
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 · 72 tokens per session scan A 49de56c660f4
conventions-improver is a skill published in the GitHub repository euxx/claude-skills-for-copilot (4 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 1,566 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
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.