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 agentmods add skills/sebastiendegodez/copilot-instructions/analyzing-codenpx skills add SebastienDegodez/copilot-instructions --skill analyzing-codegit clone --depth 1 https://github.com/SebastienDegodez/copilot-instructionsWhat 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 | $0.00026 | $0.00903 |
| Opus 5 | $0.00013 | $0.00451 |
| Sonnet 5 | $0.00005 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
analyzing-code 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 3d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tokei: Code Statistics Analysis
Always invoke analyzing-code skill for code statistics - do not execute bash commands directly.
Use tokei for fast, accurate code statistics across multiple languages and projects.
Default Strategy
Invoke analyzing-code skill for analyzing code statistics by language. Use when understanding project composition, measuring change impact before refactoring, or generating CI/CD metrics.
Common workflow: analyzing-code skill → other skills (finding-files, querying-json, querying-yaml) for filtering or analyzing-code skill after refactoring to measure impact.
Key Options
Basic Output Control
-f/--filesshow individual file statistics-l/--languageslist supported languages and extensions-v/--verboseshow unknown file extensions (1-3)-V/--versionshow version information--hiddeninclude hidden files-c/--columns Nset strict column width
Filtering & Exclusion
-t/--type TYPESfilter by language types (comma-separated)-e/--exclude PATTERNSexclude files/dirs (gitignore syntax)--no-ignoredon't respect ignore files--no-ignore-dotdon't respect .ignore/.tokeignore--no-ignore-vcsdon't respect VCS ignore files--no-ignore-parentdon't respect parent ignore files
Output Formats
-o/--output FORMAToutput format (json|yaml|cbor)- Requires compilation with features:
cargo install tokei --features all
- Requires compilation with features:
-i/--input FILEread from previous tokei run or stdin
Sorting Options
-s/--sort COLUMNsort by column- Possible values:
files|lines|blanks|code|comments
- Possible values:
Detailed Reference
For comprehensive usage patterns, output formats, language filtering, and integration examples, load tokei guide when needing:
- Advanced language filtering and exclusion
- JSON/YAML output processing
- CI/CD integration patterns
- Docker usage examples
- Performance tuning for large codebases
The guide includes:
- Basic usage and output control options
- Language filtering and exclusion patterns
- Output format configuration (JSON, YAML, CBOR)
- Performance tips for large codebases
- Docker usage and CI/CD integration
- Configuration files and environment variables
What ships with it
1 file 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.
- 3d ago First seen · 95 lines · 26 tokens per session scan A af7a374a5670
analyzing-code is a skill published in the GitHub repository SebastienDegodez/copilot-instructions (192 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 903 once invoked, about $0.0001 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
cross-squad-communication
Protocol for sending queries, delegating tasks, and sharing context between independent Squad instances across different repositories.
distributed-mesh
How to coordinate with squads on different machines using git as transport.
squad-commands
Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when the user asks for available commands or help.
economy-mode
Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.
notification-routing
Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding.
fact-checking
Review and validate claims using counter-hypothesis testing. Use when verifying technical content, checking references, validating API endpoints, or performing quality assurance on deliverables.