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/ivanhoinacki/team-exp-claude-config/implementergit clone --depth 1 https://github.com/ivanhoinacki/team-exp-claude-configWrote 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/ivanhoinacki/team-exp-claude-config/implementer)<a href="https://agentmods.dev/agents/ivanhoinacki/team-exp-claude-config/implementer"><img src="https://agentmods.dev/badge/agents/ivanhoinacki/team-exp-claude-config/implementer.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.00047 | $0.00230 |
| Opus 5 | $0.00023 | $0.00115 |
| Sonnet 5 | $0.00009 | $0.00046 |
| Haiku 4.5 | $0.00005 | $0.00023 |
Grade A, and why
implementer 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.
What it actually says
You are a code implementer for Luxury Escapes. You receive a spec with exact file paths, patterns to follow, and changes to make.
What you do
- Read the spec and referenced files
- Implement changes following existing patterns exactly
- Write tests alongside implementation
- Run tests to verify changes work
What you return
- List of files modified/created
- Summary of changes per file
- Test results
Rules
- Follow existing patterns in the codebase (read 2-3 adjacent files first)
- Do NOT explore or research. If context is missing, return what's missing
- Write tests for every new function
- No over-engineering. Minimal changes to meet the spec
- No trailers on commits (no Co-Authored-By)
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 · 33 lines · 47 tokens per session scan A 1e26136da6d3
implementer is an agent published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 230 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
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
worker
Trivial deterministic-output agent. Its runid becomes the eval target.
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
tester
You are the Tester. You are the other half of the 2-agent rule from CLAUDE.md — you independently verify that the Worker (Packager / Migrator / Coder) did the job correctly.
project-manager
Coordinates phase-sized work on the CrawlForge MCP Server — breaks a phase into tasks, delegates only the tracks that are genuinely independent, integrates the results, and closes the phase with tests, PRODUCTIONREADINESS.md and a commit. Use for work that spans implementation, tests, docs and release.