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 instructions/arijeetganguli/agent-code-tracker/copilot-instructionsgit clone --depth 1 https://github.com/arijeetganguli/agent-code-trackerWhat 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.00348 | $0.00348 |
| Opus 5 | $0.00174 | $0.00174 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
agent-code-tracker copilot-instructions.md 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 2d 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.
What it actually says
Agent Code Tracker - VS Code Extension Development
Progress Checklist
- Verify that the copilot-instructions.md file in the .github directory is created
- Clarify Project Requirements - Building a VS Code extension to track percentage of code written by AI agents
- Scaffold the Project - Creating VS Code extension structure with TypeScript
- Customize the Project - Implement core tracking functionality
- Install Required Extensions - No additional extensions needed
- Compile the Project - Successfully compiled with esbuild
- Create and Run Task - Optional for testing
- Launch the Project - Press F5 to debug the extension
- Ensure Documentation is Complete - README.md updated with comprehensive information
Project Overview
VS Code extension to track and calculate the percentage of code written by AI agents (like GitHub Copilot) versus manual code contributions.
Key Features
- Monitor code changes in real-time
- Detect AI-generated vs manual code
- Track statistics per file and workspace-wide
- Display percentage in status bar
- Provide detailed statistics view
Project Structure
src/extension.ts- Main extension activation and command registrationsrc/codeTracker.ts- Core tracking logic with smart detection heuristicssrc/statusBar.ts- Status bar item managementsrc/statsView.ts- Webview for detailed statistics display
Next Steps
- Press F5 to launch the extension in debug mode
- Test the extension in a new VS Code window
- Start coding to see statistics update in real-time
- Use Command Palette to view detailed statistics
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.
- 2d ago First seen · 37 lines · 348 tokens per session scan A 68ff680fd8f0
agent-code-tracker copilot-instructions.md is an instructions file published in the GitHub repository arijeetganguli/agent-code-tracker (2 stars, last pushed 1mo ago), licensed MIT. It adds 348 tokens to every session, about $0.0017 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-31.
Other instructions, from other repositories
asana-project-ops CLAUDE.md
Instructions for n0zer0d4y/asana-project-ops, covering claude.md, build and development commands, build the project (uses esbuild), run in development mode with ts-node (requires node.js 18+) and start the built server.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).