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/eddiebelaval/squireWrote 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/eddiebelaval/squire/kb-search)<a href="https://agentmods.dev/commands/eddiebelaval/squire/kb-search"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/kb-search.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.1 | $0.00000 | $0.00559 |
| Opus 5 | $0.00000 | $0.00280 |
| Sonnet 5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
kb-search 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 5d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/kb-search -- Knowledge Base Search
You search across id8Labs knowledge bases for articles matching a query. Faster than /kb-query -- this finds what exists, not synthesizes answers.
Arguments: $ARGUMENTS
Route by Arguments
Parse $ARGUMENTS:
| Input | Action |
|---|---|
<term> |
Search all KBs for articles matching the term |
<term> --kb <name> |
Search a specific KB only |
<term> --type <concepts|sources|connections> |
Filter by article type |
| (empty) | Show KB stats (article counts per KB) |
Setup
- Read
~/Development/id8/knowledge/manifest.json - For each target KB, read
wiki/_index.md
Search Process
Step 1: Load Indexes
For each target KB:
- Read
{kb}/wiki/_index.md - Parse all article entries (the
[[wikilinks]]and their descriptions) - Build a flat list of:
{kb_name, article_path, display_name, description, type}
Step 2: Fuzzy Match
Search the flat list against the query term:
- Match against display name, description, and article type
- Case-insensitive substring matching
- Also search frontmatter tags if articles have them (read the first 10 lines of each matching candidate)
- Rank by relevance: exact title match > title contains > description contains > tag match
Step 3: Deep Search (if few results)
If fewer than 3 matches from index search:
- Use Grep to search inside
wiki/**/*.mdfor the term - Report files that contain the term with a snippet of context
- This catches content that isn't surfaced in the index descriptions
Step 4: Report
Display results grouped by KB:
## Search: "{term}"
### research (N matches)
- [[concepts/constraint-as-consciousness|Constraint as Consciousness]] -- F-005, write-protection as precondition
- [[registries/findings|Findings Registry]] -- contains 2 mentions
### design (N matches)
- [[concepts/shadow-as-border|Shadow-as-Border]] -- Vercel's 0px 0px 0px 1px pattern
- [[sources/vercel|Vercel]] -- shadow-as-border technique
### memory (N matches)
- (none)
Total: N articles across M knowledge bases
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.
- 5d ago First seen · 75 lines · 0 tokens per session scan A 657e840ba38d
kb-search is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 559 tokens. 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
paul:help
Show available PAUL commands and usage guide.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
analizar-sesiones
Analizar sesiones de Claude en el equipo para extraer patrones de uso y generar recomendaciones de habilidades, plugins, agentes y reglas.
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…
iniciar
Inicializar Don Cheli en un proyecto nuevo o existente.
archivar
Archivar specs completadas y sincronizar delta specs con specs principales.