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/lglucas/ai-dev-operating-system/codemapnpx skills add lglucas/ai-dev-operating-system --skill codemapgit clone --depth 1 https://github.com/lglucas/ai-dev-operating-systemWrote 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/lglucas/ai-dev-operating-system/codemap)<a href="https://agentmods.dev/skills/lglucas/ai-dev-operating-system/codemap"><img src="https://agentmods.dev/badge/skills/lglucas/ai-dev-operating-system/codemap.svg" alt="Measured on agentmods" 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 | $0.00130 | $0.01091 |
| Opus 5 | $0.00065 | $0.00545 |
| Sonnet 5 | $0.00026 | $0.00218 |
| Haiku 4.5 | $0.00013 | $0.00109 |
Grade A, and why
codemap 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codemap
Antes de procurar, leia o mapa
Se você está prestes a varrer o projeto atrás de um arquivo — pare e leia o CODEMAP.md primeiro. É uma leitura contra dezenas. É literalmente para isso que ele existe.
Se o arquivo não existir, verifique o marcador .aios-self antes de estranhar: dentro do repositório do próprio AI Dev OS não há mapa por design (veja Escopo), e nesse caso procurar direto é o certo. Em projeto derivado, mapa ausente significa que ninguém rodou o gerador ainda — rode.
Se o mapa existe mas não responde, aí sim procure. E quando achar, considere se a descrição daquele arquivo estava ruim: o conserto é melhorar o cabeçalho Purpose: dele.
Regenerar
node scripts/codemap.js
Sobrescreve o CODEMAP.md inteiro. Nunca edite o arquivo à mão — a próxima geração desfaz.
Para verificar sem escrever, como o CI faz:
node scripts/codemap.js --check
Quando regenerar
| Momento | Por quê |
|---|---|
| Criou, removeu, renomeou ou moveu arquivo de código | a lista fica errada na hora |
Mudou o Purpose: de um arquivo |
a descrição no mapa fica velha |
| Mudou o número de linhas de um arquivo | o mapa grava a contagem exata |
| Ao fechar sprint | sprint-management já toca changelog e docs; o mapa vai junto |
| Antes de release | release-check delega para cá |
| Depois de refatoração que moveu arquivos | é quando o mapa mais diverge |
A terceira linha é a que pega desprevenido: como o mapa grava a contagem exata, editar o corpo de um arquivo já mapeado costuma bastar para o --check acusar divergência. Regenere junto com a mudança e comite os dois — é mais barato que descobrir pelo CI vermelho.
O limite de 200 linhas continua sendo só um aviso no mapa, não o gatilho da regeneração. O gatilho é a contagem mudar, qualquer que seja o valor.
De onde vem a descrição
Do cabeçalho que a code-style já exige:
/**
* Purpose: o que este arquivo resolve, em uma frase.
* Version: v0.1.0
* Sprint: 01
*/
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.
- 4d ago First seen · 84 lines · 130 tokens per session scan A 005663630c2b
codemap is a skill published in the GitHub repository lglucas/ai-dev-operating-system (11 stars, last pushed 25d ago), licensed MIT. It adds 130 tokens to every session and 1,091 once invoked, about $0.0006 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
design-system
Generate a complete design system (design.md, design-guidelines.md, design-components.md) from any reference materials — images, PDFs, links, or descriptions.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
sidewinder-rattlesnake
Adversary-emulation profile for SideWinder (G0121 / Rattlesnake / T-APT-04 / Razor Tiger), India's suspected state-sponsored cyber-espionage actor.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
omh-code-review
This is a Hermes-native code-review workflow skill.