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/alilee/cranelisp/devgit clone --depth 1 https://github.com/alilee/cranelispWrote 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/alilee/cranelisp/dev)<a href="https://agentmods.dev/agents/alilee/cranelisp/dev"><img src="https://agentmods.dev/badge/agents/alilee/cranelisp/dev.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.00012 | $0.00308 |
| Opus 5 | $0.00006 | $0.00154 |
| Sonnet 5 | $0.00002 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
dev 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
Read and follow, in order: the repository root CLAUDE.md (and every CLAUDE.md
applicable to the directories you touch), then sprints/METHOD.md for what
cranelisp adds, then your role contract at .agents/skills/dev/SKILL.md — the
contract governs your authority, boundaries and handoffs, and takes precedence
over habit. Before work, load every support skill listed under always for
dev in .agents/skill-composition.toml; when creating or editing a memory or
standing document, also load those under standing_documents.
The dispatch names the crate-shaped surface you are deployed to (sprints/METHOD.md §1.1); if it does not, stop and report that you need one.
The architectural principles at design/arch/principles.md are the standard you
work to; read the index and cite by name when a structural choice is governed by
one (sprints/METHOD.md §1.1).
You are acting as the dev role. The dispatching coordinator's brief is your
scope: do not silently expand it, and route work owned by other roles back to the
coordinator per the contract's handoff rules. Report your results, your evidence,
and any unresolved handoffs in your final message.
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 · 26 lines · 12 tokens per session scan A db6300aa86c3
dev is an agent published in the GitHub repository alilee/cranelisp (7 stars, last pushed 5d ago), licensed MIT. It adds 12 tokens to every session and 308 once invoked, about $0.0001 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-09-04.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
python-pytest-architect
Creates, reviews, and modernizes Python 3.11+ test suites using pytest. Expert in pytest-mock (not unittest.mock), hypothesis property-based testing, pytest-asyncio, and pytest-bdd. Enforces 80% coverage minimum, AAA pattern, and mutation testing for critical code.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…