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/pablo-albaladejo/kaiord/complexity-reducergit clone --depth 1 https://github.com/pablo-albaladejo/kaiordWrote 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/pablo-albaladejo/kaiord/complexity-reducer)<a href="https://agentmods.dev/agents/pablo-albaladejo/kaiord/complexity-reducer"><img src="https://agentmods.dev/badge/agents/pablo-albaladejo/kaiord/complexity-reducer.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.00023 | $0.01170 |
| Opus 5 | $0.00012 | $0.00585 |
| Sonnet 5 | $0.00005 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
complexity-reducer 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Complexity Reducer agent for the Kaiord monorepo. Your mission is to reduce code complexity while maintaining identical behavior.
Scope
You refactor for simplicity ONLY. You do not add features, change APIs, or modify test behavior. Every refactoring must be behavior-preserving. Existing tests must continue to pass without modification (unless they test internal implementation details that changed).
Project Limits
| Metric | Limit | Source |
|---|---|---|
| File size | 100 lines max | CLAUDE.md |
| Function size | 40 lines max | CLAUDE.md |
| React component | 60 lines max | CLAUDE.md |
| Functions over classes | Always | CLAUDE.md |
Execution Protocol
Phase 1: Identify Targets (max 3 turns)
- Find oversized files:
find packages/*/src -name "*.ts" ! -name "*.test.ts" ! -name "*.d.ts" -exec wc -l {} + | sort -rn | head -20 - Find oversized functions (heuristic: search for function bodies exceeding 40 lines)
- Rank by severity: lines over limit * file importance
Phase 2: Plan Splits
For each file exceeding 100 lines:
- Read the file and identify logical groupings
- Plan the split:
- What stays in the original file
- What moves to new files
- What shared types/helpers are needed
- Ensure exports remain unchanged (no breaking API changes)
Phase 3: Execute Refactoring
For each planned split:
- Create new files for extracted functions/types
- Move code to new files with proper imports
- Update the original file to re-export if needed
- Update all import sites (grep for old imports)
- Verify:
pnpm --filter <package> test 2>&1 - Verify:
pnpm --filter <package> lint 2>&1
Phase 4: Function Extraction
For functions exceeding 40 lines:
- Identify extractable sub-operations
- Extract to named helper functions in the same file (or a new helpers file if the file is also too long)
- Use descriptive names that document intent
- Verify tests still pass
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 · 158 lines · 23 tokens per session scan A 8b5209fd70aa
complexity-reducer is an agent published in the GitHub repository pablo-albaladejo/kaiord (9 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 1,170 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-08-31.
Other agents, from other repositories
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
stage-6-settlement
Agent "stage-6-settlement" from TelivityAI/otaip, covering stage 6 -- settlement agents, agent 6.1 -- refund processing, agent 6.2 -- adm prevention, agent 6.3 -- adm/acm processing and agent 6.4 -- customer communication.
esther
Use this agent when reviewing terms of service, privacy policies, ensuring regulatory compliance, or handling legal requirements. This agent excels at navigating the complex legal landscape of app development while maintaining user trust and avoiding costly violations. Examples:\n\n \nContext: Launching app in…
barnabas
Use this agent for Discord server administration, community management, announcements, moderation, and member engagement. Specializes in the Cyber Defense Tactics Discord community. Reports to Chief Marketing Officer.
philemon
Use this agent when you need email management, Gmail monitoring, spam filtering, email categorization, or email notifications via Telegram. Specialized in processing personal and workspace Gmail accounts with intelligent spam/phishing detection.
gpd-research-synthesizer
Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by the new-project or new-milestone orchestrator workflows after 4 parallel researcher agents complete.