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 agentmods add agents/teaql/teaql-agent-kit/error-fixgit clone --depth 1 https://github.com/teaql/teaql-agent-kitWhat 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 | $0.00000 | $0.00299 |
| Opus 5 | $0.00000 | $0.00150 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
ERROR-FIX 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 yesterday.
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.
What it actually says
TeaQL KSML Error Fixes
| Rule ID | Explanation & Fix |
|---|---|
KSML-STRUCTURE-001 |
Nested Object Definition. You placed an object tag INSIDE another object tag (e.g. <school target="school()"/> inside <platform>). In KSML, object definitions CANNOT be nested. All <foo> object definitions must be direct children of <root>. To define a relationship, use an attribute like platform="platform()" on the child object instead of nesting XML tags. Remove any nested relationship tags. |
KSML-LOG-004 |
Missing user field. A logging object (like audit_log or activity_log) MUST include a user/operator field (e.g. action_user="string()", created_by="string()"). Add a field representing the user to the log object. |
KSML-KEYWORD-002 |
Reserved keyword. The field name you used conflicts with language reserved keywords (e.g., operator, type). Rename the field to something else (e.g., action_operator, record_type). |
KSML-XML-005 |
Empty Attribute. You left an attribute empty (e.g., company_name=""). Empty values are not allowed in KSML definitions. Provide a valid type definition like company_name="string()". |
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.
- yesterday First seen · 9 lines · 0 tokens per session scan A 99835899d479
ERROR-FIX is an agent published in the GitHub repository teaql/teaql-agent-kit (2,801 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 299 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-08-30.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
code-reviewer
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).