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 gosha70/code-copilot-team --skill copilot-conventionsgit clone --depth 1 https://github.com/gosha70/code-copilot-teamWrote 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/gosha70/code-copilot-team/copilot-conventions)<a href="https://agentmods.dev/skills/gosha70/code-copilot-team/copilot-conventions"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/copilot-conventions/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/gosha70/code-copilot-team/copilot-conventions"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/copilot-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 13 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00028 | $0.01260 |
| Opus 5.5 | $0.00011 | $0.00504 |
| Sonnet 5.5 | $0.00006 | $0.00252 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
copilot-conventions 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Copilot Conventions
Shared rules that apply whether using Claude Code, GitHub Copilot, Cursor, or local LLMs. These conventions ensure consistent behaviour regardless of which AI tool is driving.
Core Contract
- Read before write — understand existing code and patterns first.
- Minimal changes — only modify what was requested.
- Show your work — explain changes, provide diffs.
- Test everything — run linters and tests after code changes.
- Ask when uncertain — do not guess at ambiguous requirements.
- Verify before diagnosing — when asked to fix a reported bug, re-run the failing test or reproduce the symptom first. The issue may already be fixed. Do not spend time diagnosing a problem that no longer exists.
Target Alignment and Complexity Control
Before planning, implementing, or approving agent-produced work:
- Restate the originating goal and concrete acceptance criteria. Derived plans and agent summaries do not replace the original request.
- Map every changed file and each new abstraction, interface, state, dependency, or test layer to a current requirement or a concrete correctness or safety failure. Remove or defer anything without that link.
- Prefer the smallest solution that fits the existing architecture. Do not turn narrow work into a framework, generalized engine, speculative state model, broad hardening exercise, or unrelated cleanup.
- Keep tests, documentation, and proof proportional to the risk and acceptance criteria. More artifacts are not evidence of better alignment.
- Complete the required path before optional improvements. Record useful extras as follow-up work instead of silently expanding scope.
- Before approval, ask: What can be removed without weakening correctness, safety, or the acceptance criteria?
For a handoff from Claude Code or any other agent, explicitly classify the change as on-target, overcomplicated, or off-target, and explain the evidence. Green tests do not compensate for scope drift. Judge the artifact rather than guessing at a vendor's intent; complexity required by a concrete failure mode is not overengineering when the link is explicit.
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 · 88 lines · 28 tokens per session scan A 09e3477deb29
copilot-conventions is a skill published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 17d ago), licensed MIT. It adds 28 tokens to every session and 1,260 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-09-03.
Other skills, from other repositories
agent-deck
Helper scripts live in this skill's scripts/ folder. Resolve them from the base directory shown when the skill loaded, not from the user's project.
contributor
End-to-end open source contribution workflow: from scanning issues to submitting PRs. Use this skill whenever the user wants to contribute to an open source project, find issues to fix, submit a pull request, fork a repo to contribute, fix a GitHub issue, or mentions 'open source contribution'. Also trigger when they…
git-commit-smart
Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.
push-all
Use when the user explicitly asks to stage all current changes, create a commit, and push to the remote after safety checks.
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…
dev-architecture-playbook
Route full software-development architecture work from product intent through design, implementation, testing, release, and operations. Use when the user asks for a complete development architecture, wants to know which Spellbook skills to combine, needs an execution path across…