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-ingest)<a href="https://agentmods.dev/commands/eddiebelaval/squire/kb-ingest"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/kb-ingest.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.00736 |
| Opus 5 | $0.00000 | $0.00368 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
kb-ingest 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/kb-ingest -- Knowledge Base Ingest
You ingest raw source material into an id8Labs knowledge base for later compilation.
Arguments: $ARGUMENTS
Route by Arguments
Parse $ARGUMENTS:
| Input | Action |
|---|---|
<kb-name> <file-path> |
Ingest a local file |
<kb-name> <url> |
Fetch and ingest a web page (uses defuddle) |
<kb-name> --paste |
Ingest pasted content from the user's next message |
<kb-name> status |
Show raw/ inventory (processed vs unprocessed) |
| (empty) | Show help |
Setup
- Read
~/Development/id8/knowledge/manifest.json - Locate the target KB
- Check KB type: if
mirror, reject ingest (read-only). Ifread_only_raw, reject ingest to raw (suggest manual addition to source repo). - Read
~/.claude/skills/knowledge/SKILL.mdfor article templates
Ingest Process
For Local Files
- Read the source file
- Generate a slug from the content title or filename (kebab-case, max 40 chars)
- Copy to
{kb}/raw/{slug}.mdwith frontmatter:
---
source_url: "local"
source_path: "{original file path}"
source_type: {article | paper | repo | dataset | image | reference}
ingested: YYYY-MM-DD
processed: false
---
{file contents}
For URLs
- Use the defuddle skill to fetch and convert the web page to clean markdown
- Generate a slug from the page title
- Save to
{kb}/raw/{slug}.mdwith frontmatter:
---
source_url: "{url}"
source_type: article
ingested: YYYY-MM-DD
processed: false
---
{defuddled markdown content}
- If the page has images, note their URLs in the frontmatter for potential later download
For Paste
- Prompt user: "Paste the content you want to ingest."
- Accept the content
- Ask for a title if not obvious from content
- Save to
{kb}/raw/{slug}.mdwith frontmatter (source_url: "paste")
Post-Ingest
After saving the raw file:
- Report: "Ingested
{filename}to{kb}/raw/. Source type: {type}." - Quick scan: extract 3-5 key topics/claims from the source
- Check against existing
wiki/_index.mdfor overlap: "This relates to existing articles: [[concept-x]], [[concept-y]]" - Suggest: "Run
/kb-compile {kb-name}to process this into wiki articles."
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 · 103 lines · 0 tokens per session scan A fbd2b6f241cb
kb-ingest 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 736 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.