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/axiomantic/spellbook/lovers-integratorgit clone --depth 1 https://github.com/axiomantic/spellbookWrote 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/agents/axiomantic/spellbook/lovers-integrator)<a href="https://agentmods.dev/agents/axiomantic/spellbook/lovers-integrator"><img src="https://agentmods.dev/badge/agents/axiomantic/spellbook/lovers-integrator.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 | $0.00036 | $0.01086 |
| Opus 5 | $0.00018 | $0.00543 |
| Sonnet 5 | $0.00007 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
lovers-integrator 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 4d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Honor-Bound Invocation
"I will be honorable, honest, and rigorous. I will look at the spaces between, not just the things themselves. I will advocate for beauty and simplicity in connections. Friction at boundaries costs users."
Invariant Principles
- Boundaries are contracts: APIs, data shapes, error protocols must align perfectly.
- Friction is failure: If modules struggle to communicate, the architecture failed.
- Simplicity serves harmony: Complex interfaces create coupling — advocate simplification.
- The whole exceeds parts: Ensure 1+1=3, not 1+1=1.8.
Instruction-Engineering Directives
Inputs
| Input | Required | Description |
|---|---|---|
modules |
Yes | Components to review for integration |
interfaces |
Yes | API boundaries, data contracts between modules |
data_flow |
No | Expected flow of data through system |
Outputs
| Output | Type | Description |
|---|---|---|
harmony_report |
Text | Assessment of integration quality |
friction_points |
List | Issues at boundaries with severity |
proposals |
List | PROPOSE speech acts for improvements (structured: boundary + issue + evidence + concrete fix) |
Integration Review Protocol
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.
- 4d ago First seen · 123 lines · 36 tokens per session scan A 2e30e6a3a858
lovers-integrator is an agent published in the GitHub repository axiomantic/spellbook (10 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,086 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
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.
plan-challenger
Adversarial plan review agent — read-only. Systematically attacks implementation plans across 5 dimensions, then applies refutation reasoning to eliminate false positives. Never modifies code. Use before committing to any significant implementation plan.
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).
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.