Borrowing it
Nothing to install: this file belongs to pablo-albaladejo/kaiord. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pablo-albaladejo/kaiord/main/.claude/agents/README.mdgit 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/readme)<a href="https://agentmods.dev/agents/pablo-albaladejo/kaiord/readme"><img src="https://agentmods.dev/badge/agents/pablo-albaladejo/kaiord/readme.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.00000 | $0.01120 |
| Opus 5 | $0.00000 | $0.00560 |
| Sonnet 5 | $0.00000 | $0.00224 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
README 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 6d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Agents
This directory contains specialized AI agents for the Kaiord project. Agents are different from skills - they are autonomous workflows that orchestrate multiple skills and tools to accomplish complex tasks.
Available Agents
NPM Optimizer Agent
File: npm-optimizer.md
Purpose: Comprehensive npm package optimization
What it does:
- Analyzes dependencies (unused, duplicates, security)
- Checks bundle sizes against thresholds
- Identifies import optimization opportunities
- Generates prioritized action plans
- Provides implementation commands
When to use:
- Before creating PRs
- After adding new dependencies
- Weekly maintenance reviews
- When bundle sizes seem large
- When you want a complete health check
How to invoke: Agents are invoked using the Task tool with the agent's context. Claude Code will automatically detect and use the agent definition.
Example prompt:
I need a comprehensive npm optimization review of all packages.
Use the NPM Optimizer Agent.
Capabilities:
- Orchestrates
/check-deps,/analyze-bundle,/optimize-importsskills - Cross-package analysis
- Security auditing
- Architecture validation
- Prioritized issue reporting
Output: Generates a comprehensive markdown report with:
- Executive summary with health score (0-10)
- Per-package detailed findings
- Cross-package patterns and duplicates
- Prioritized action plan (Critical/High/Medium/Low)
- Ready-to-run bash commands
Creating New Agents
Agent Structure
Agents are markdown files with:
- Clear role definition - What the agent specializes in
- Capabilities - What skills/tools it can use
- Workflow - Step-by-step execution plan
- Quality standards - What standards it must follow
- Communication style - How it presents information
- Success criteria - How to measure success
Best Practices
DO:
- ✅ Define clear scope and responsibilities
- ✅ List all available skills/tools
- ✅ Provide structured workflow (phases)
- ✅ Include example interactions
- ✅ Specify output format
- ✅ Follow project quality standards
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.
- 6d ago First seen · 237 lines · 0 tokens per session scan A 63ad849ccc2e
README is an agent published in the GitHub repository pablo-albaladejo/kaiord (9 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,120 tokens. 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
pre-commit-reviewer
Use this agent to review code changes before committing and pushing to a PR. This agent analyzes diffs for bugs, style issues, dead code, missing tests, and alignment with target repository conventions. Use as a fallback when the PR review toolkit is unavailable, or dispatch directly for standalone pre-commit review.
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
gpd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality for physics research. Spawned by the plan-phase and verify-work workflows.
harness-typescript-strict-reviewer
Framework-aware reviewer for TypeScript diffs — flags type holes, refactor regressions, complexity growth, and five-second-rule names.
agent-sdk-verifier-ts
Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.