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/mathieu0905/skilllens/agents-mdgit clone --depth 1 https://github.com/mathieu0905/skilllensWhat 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.00208 | $0.00208 |
| Opus 5 | $0.00104 | $0.00104 |
| Sonnet 5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
skilllens AGENTS.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.
Copies of this mod
1 near-identical copy found in the catalogue:
- skilllens CLAUDE.md — 98% identical, 2 lines differ
What it actually says
Agent Collaboration Rules
Version Management
- Use git commits to version SkillScope code, analyzer logic, optimizer prompts, and workflow rules.
- Do not manage logic history by creating endless
v1,v2,v3,v8directories or constants. That makes rollback and comparison noisy. - Use git revert, branches, tags, and commit hashes for rollback or comparison.
- Keep experiment artifacts under semantic names that describe intent, such as
fresh-from-original,native-target-split, orcia-batch-smoke. - Every experiment artifact should record the code commit, analyzer version or schema version, source skill path, trace path, and native verifier result.
- Only bump explicit schema/analyzer version strings when cache compatibility or persisted data format genuinely changes.
- Temporary numbered directories are allowed only for short-lived scratch work. Promote useful results into a semantic run name or a database record, then clean up redundant copies.
Principle
Experiment outputs are data. Git history is the version manager.
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 · 16 lines · 208 tokens per session scan A 8539c112fb3c
skilllens AGENTS.md is an instructions file published in the GitHub repository mathieu0905/skilllens (2 stars, last pushed 2mo ago), licensed MIT. It adds 208 tokens to every session, about $0.0010 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
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.
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).
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.