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-query)<a href="https://agentmods.dev/commands/ricneves-ai/flowgrammers-skills/wiki-query"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/wiki-query/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-query"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/wiki-query.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.00062 | $0.00639 |
| Opus 5 | $0.00031 | $0.00319 |
| Sonnet 5 | $0.00012 | $0.00128 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
wiki-query 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wiki-query
Faça uma pergunta ao wiki. O bibliotecário lê primeiro index.md, seleciona páginas relevantes entre categorias, sintetiza uma resposta com citações e oferece registrar a resposta de volta no wiki para que suas explorações se acumulem.
Uso
/wiki-query "<sua pergunta>"
/wiki-query "o que o wiki diz sobre sparse autoencoders?"
/wiki-query "compare monosemanticity e polysemanticity nas minhas fontes"
/wiki-query "quais fontes discordam sobre leis de escala?"
/wiki-query "dê-me uma tabela comparativa de SAE vs linear probing"
O que acontece
- Leitura do índice primeiro — lê
wiki/index.mdpara encontrar páginas relevantes - Aprofundamento — lê 3 a 10 páginas completas (síntese + conceitos + fontes + entidades)
- Seguimento de links — segue wikilinks entre páginas oportunisticamente
- Busca fallback — se o índice não for suficiente, executa
scripts/wiki_search.py(BM25) - Síntese — compõe uma resposta direta + detalhe de suporte + citações
[[sources/xxx]]inline + seção "Páginas relacionadas" - Oferta de registro — pergunta se deve salvar como nova página wiki (geralmente em
comparisons/ousynthesis/)
Formatos de saída
O formato da resposta segue a pergunta:
| Formato da pergunta | Saída |
|---|---|
| "O que é X?" | Explicação em markdown com citações |
| "A vs B" | Tabela comparativa |
| "Faça um slide sobre X" | Síntese em markdown → /wiki-marp para renderizar |
| "Mostre a tendência de X" | Script Python + gráfico salvo em wiki/assets/charts/ |
Sub-agente
Este comando despacha o sub-agente wiki-librarian. Veja agents/wiki-librarian.md.
Scripts
engineering/llm-wiki/scripts/wiki_search.py— busca BM25 como fallbackengineering/llm-wiki/scripts/append_log.py— registra respostas arquivadas
Regras
- Leia o índice primeiro. Nada de grep em tudo.
- Cada afirmação cita uma página com um
[[wikilink]]. - Ofereça registrar a resposta de volta — mas apenas para respostas substantivas que valham ser mantidas.
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 · 59 lines · 0 tokens per session scan A 5df1306a3e8b
wiki-query is a command published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 639 once invoked, about $0.0003 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
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-13-4.en
Welcome to Lesson 13-4: Landing Page Implementation!
start-0-8
A Japanese-language command that displays the current project setup progress.