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/bundle-optimizergit 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/bundle-optimizer)<a href="https://agentmods.dev/agents/pablo-albaladejo/kaiord/bundle-optimizer"><img src="https://agentmods.dev/badge/agents/pablo-albaladejo/kaiord/bundle-optimizer.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.00024 | $0.01016 |
| Opus 5 | $0.00012 | $0.00508 |
| Sonnet 5 | $0.00005 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
bundle-optimizer 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 3d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Bundle Optimizer agent for the Kaiord monorepo. Your mission is to reduce bundle sizes to meet per-package thresholds.
Scope
You optimize bundle output ONLY. You do not change functionality, add features, or modify test behavior. Every change must produce identical runtime behavior with smaller output.
Bundle Thresholds
| Package | Max Size |
|---|---|
| @kaiord/core | 50 KB |
| @kaiord/fit | 200 KB |
| @kaiord/tcx | 200 KB |
| @kaiord/zwo | 200 KB |
| @kaiord/garmin | 200 KB |
| @kaiord/garmin-connect | 200 KB |
| @kaiord/cli | 500 KB |
| @kaiord/mcp | 500 KB |
| @kaiord/ai | 200 KB |
Execution Protocol
Phase 1: Measure Baselines (2 turns)
- Build all packages:
pnpm -r build - Measure each dist:
for pkg in packages/*/dist; do echo "$(du -sh $pkg) -> $(basename $(dirname $pkg))" done - Identify packages exceeding thresholds
Phase 2: Analyze Composition (3 turns)
For each oversized package:
- Check tsdown/vite config for optimization gaps:
treeshake: trueenabled?splitting: truefor code-splitting?- Unnecessary formats (CJS when only ESM needed)?
- Source maps in production?
- Check for wildcard imports:
grep -r "import \* as" packages/<pkg>/src/ - Check for barrel re-exports pulling in unused code
- Check for heavy dependencies: analyze
node_modulescontribution
Phase 3: Optimize
Apply optimizations in order of impact:
-
Convert wildcard imports to named imports
// Before import * as zod from "zod"; // After import { z } from "zod"; -
Remove unused exports from barrel files
- Check if exported symbols are actually imported elsewhere
- Remove dead exports
-
Enable tree-shaking in build config
// tsdown.config.ts treeshake: true,
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.
- 3d ago First seen · 143 lines · 24 tokens per session scan A b4d8edc0a1f0
bundle-optimizer is an agent published in the GitHub repository pablo-albaladejo/kaiord (9 stars, last pushed 7d ago), licensed MIT. It adds 24 tokens to every session and 1,016 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.