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 tatagoncalvesof/imperatriz-toolkit --skill glossariodatatagit clone --depth 1 https://github.com/tatagoncalvesof/imperatriz-toolkitWrote 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/tatagoncalvesof/imperatriz-toolkit/glossariodatata)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/glossariodatata"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/glossariodatata/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/tatagoncalvesof/imperatriz-toolkit/glossariodatata"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/glossariodatata.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00089 | $0.02041 |
| Opus 5 | $0.00044 | $0.01020 |
| Sonnet 5 | $0.00018 | $0.00408 |
| Haiku 4.5 | $0.00009 | $0.00204 |
Grade C, and why
glossariodatata scanned grade C with 1 finding 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 11d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- VPS path: `/var/www/apps/glossariodatata/` (acesso via `ssh -i ~/.ssh/id_ed25519_hostinger [email protected]`) How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Glossariodatata — Gerenciador do Glossário Tech da Tata
Sobre
O Glossário é um sistema de 3 camadas com fonte única de verdade:
glossario.json ◄── FONTE ÚNICA DE VERDADE (edita só aqui)
↓
├─→ index.html (site — lê JSON via fetch)
└─→ Glossario-Imperatriz-Tech.md (vault — gerado por script)
Paths:
- Projeto local:
~/Documents/Obsidian Vault/03 - Projetos/Glossario-Tata-Site/glossario.json— dadosindex.html— sitegenerate-md.mjs— regenera MDdeploy.sh— upload pra VPS
- MD gerado:
~/Documents/Obsidian Vault/08 - Recursos/Glossario-Imperatriz-Tech.md - VPS path:
/var/www/apps/glossariodatata/(acesso viassh -i ~/.ssh/id_ed25519_hostinger [email protected]) - URL pública:
https://mentoriaimperioia.com/glossariodatata/
Ações suportadas
1. /glossariodatata add <termo> — Adicionar termo novo
Quando usuária pedir pra adicionar um termo (ex: "adiciona 'Kubernetes' no glossário"):
- Ler
~/Documents/Obsidian Vault/03 - Projetos/Glossario-Tata-Site/glossario.json - Verificar se o termo já existe (case-insensitive em
name) - Se já existe, confirmar com usuária se quer atualizar ou abortar
- Se novo, decidir a categoria certa entre as 17 existentes baseado no conceito
- Escrever os 4 campos seguindo o padrão:
name: nome canônico do termotag: tag curta (ex: "Conceito", "Ferramenta", "Erro", "React")what: definição técnica em 1-2 frases (linguagem simples)analogy: analogia do mundo real, preferencialmente de restaurante/casa/vida cotidianauses: conexão com o ecossistema REAL da Tata (projetos: Marketing Command, Escritório Império, Ana Lazarotto, VPS Hostinger, skills Claude Code, etc). Se não se aplica ao stack dela, dizer "potencial" ou "não aplica ao seu stack atual".
- Inserir no array
termsda categoria escolhida - Atualizar
updatedAtpara a data de hoje - Rodar
cd "~/Documents/Obsidian Vault/03 - Projetos/Glossario-Tata-Site" && ./deploy.sh - Confirmar deploy com URL + contagem nova
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.
- 11d ago First seen · 146 lines · 89 tokens per session scan C dbf771d2874c
glossariodatata is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 89 tokens to every session and 2,041 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
test-review
Test coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
feature-dev
Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.