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.
git clone --depth 1 https://github.com/ricneves-ai/flowgrammers-skillsWrote 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/commands/ricneves-ai/flowgrammers-skills/wiki-lint)<a href="https://agentmods.dev/commands/ricneves-ai/flowgrammers-skills/wiki-lint"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/wiki-lint/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/commands/ricneves-ai/flowgrammers-skills/wiki-lint"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/wiki-lint.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.00108 | $0.00758 |
| Opus 5 | $0.00054 | $0.00379 |
| Sonnet 5 | $0.00022 | $0.00152 |
| Haiku 4.5 | $0.00011 | $0.00076 |
Grade A, and why
wiki-lint 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 9d 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.
/wiki-lint
Verifica a saúde do wiki. Identifica páginas órfãs, wikilinks quebrados, afirmações desatualizadas, frontmatter ausente, contradições e desvios estruturais. Reporta, não corrige silenciosamente — você decide o que alterar.
Execute semanalmente, após ingestões em lote e sempre antes de compartilhar o wiki.
Uso
/wiki-lint
/wiki-lint --stale-days 60
/wiki-lint --log-gap-days 7
O que acontece
Passagem 1 — Mecânica (scripts)
scripts/lint_wiki.py— páginas órfãs, links quebrados, páginas desatualizadas, frontmatter ausente, títulos duplicados, lacuna no logscripts/graph_analyzer.py— hubs, sinks, componentes conectados, estatísticas do grafo
Passagem 2 — Semântica (LLM lê e analisa)
- Contradições entre páginas atualizadas recentemente
- Afirmações desatualizadas superadas por fontes mais recentes
- Conceitos mencionados em texto simples em 3+ páginas sem página própria
- Lacunas de referência cruzada (entidades mencionadas mas não vinculadas via wikilink)
- Desvio do índice (index.md fora de sincronia com wiki/)
Passagem 3 — Relatório
Um relatório markdown agrupado por severidade:
# Wiki lint — <data>
**Total de páginas:** N **Componentes:** N **Último log:** <data>
## Encontrado
- ⚠️ <N> contradições (lista)
- <N> páginas órfãs
- <N> links quebrados
- <N> páginas desatualizadas
- ...
## Ações sugeridas
1. Investigar contradição entre [[sources/a]] e [[sources/b]]
2. Criar página de conceito para "<nome>"
3. Corrigir link quebrado em [[concepts/x]]
4. Re-ingerir [[sources/c]] — desatualizado + contraditado
5. ...
Em seguida, acrescenta uma entrada lint ao log.md.
Sub-agente
Despacha o sub-agente wiki-linter. Veja agents/wiki-linter.md.
Scripts
engineering/llm-wiki/scripts/lint_wiki.pyengineering/llm-wiki/scripts/graph_analyzer.pyengineering/llm-wiki/scripts/append_log.py
Frequência
| Gatilho | Passagem |
|---|---|
| Semanal | Apenas mecânica — rápida |
| Após ingestão em lote | Completa (mecânica + semântica) |
| Mensal | Completa + revisão estrutural |
| Antes de compartilhar | Completa + revisão extra |
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.
- 9d ago First seen · 84 lines · 0 tokens per session scan A 050f2b62a840
wiki-lint is a command published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 108 tokens to every session and 758 once invoked, about $0.0005 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-09-03.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.