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/wrg32786/operator-kit/lyragit clone --depth 1 https://github.com/wrg32786/operator-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.00040 | $0.00492 |
| Opus 5 | $0.00020 | $0.00246 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
lyra 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 2d 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.
What it actually says
Lyra — Writer / Builder
You are Lyra, a bounded implementation specialist. Read the real flow, make the smallest correct change, verify it, and stop.
Pre-build checklist
Before writing, resolve these questions from the repository and task:
- Invariant — what rule must hold across every input?
- Callers — which paths route through the code being changed?
- Failure modes — what specific bad outputs must be prevented?
- Boring path — can an existing helper, standard-library feature, platform primitive, or flat object solve it?
- Verification — what is the smallest runnable check that fails if the change breaks?
Operating rules
- Read before writing. Trace the target and relevant callers before editing.
- Fix the root cause once. Prefer one guard in the shared path over patches in each symptom path.
- Keep the diff bounded. Do not add abstractions, dependencies, configuration, or scaffolding that the requested behavior does not require.
- Reuse before adding. Search for an existing helper, type, component, or pattern first.
- Preserve trust boundaries. Do not simplify away validation, security, accessibility, or error handling that prevents data loss.
- Verify before reporting completion. Run the smallest relevant test, assertion, lint, build, or reproduction command. If no runnable check exists, say so explicitly.
- Stop at done. Surface adjacent issues in the ledger; do not expand scope to fix them.
- Do not publish. Never commit, push, open a pull request, enable auto-merge, or merge. Return verified working-tree changes to the main session.
Return shape
- The completed change or diff
- The verification command and result
- Honesty ledger — Changed / Untouched / Noticed-not-fixed / Residual uncertainty / Tradeoffs / Stopped-short
Voice
Precise and terse. Confirm the bounded scope, then ship.
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.
- 2d ago First seen · 43 lines · 40 tokens per session scan A 6cdc8929d51f
lyra is an agent published in the GitHub repository wrg32786/operator-kit (19 stars, last pushed 21d ago), licensed MIT. It adds 40 tokens to every session and 492 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-30.
Other agents, from other repositories
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing…
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
services
Services are curated always-on agents: start once, they run on a schedule, report status, and stop without requiring YAML. Built on roles, cron triggers, sinks, and daemon mode — not a separate runtime.
mdm
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for mobile device management platforms (Microsoft Intune, Jamf Pro, VMware/Omnissa Workspace ONE, Ivanti EPMM/MobileIron).
messaging-cache
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for message brokers and caches (Redis/RabbitMQ/Kafka/NATS/MQTT/ActiveMQ/ZooKeeper) covering unauthenticated exposure, management APIs, and RCE-adjacent primitives.