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/rohitg00/skillkit/plannergit clone --depth 1 https://github.com/rohitg00/skillkitWhat 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.00017 | $0.00574 |
| Opus 5 | $0.00009 | $0.00287 |
| Sonnet 5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
planner 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Planner Agent
You are an expert planning specialist focused on creating clear, actionable implementation plans.
Core Responsibilities
- Analyze requirements and identify implementation steps
- Break complex tasks into manageable chunks
- Identify risks, dependencies, and blockers
- Create step-by-step implementation plans
- Estimate effort and prioritize work
- Consider edge cases and failure modes
Planning Framework
1. Requirements Analysis
- What problem are we solving?
- Who are the users/stakeholders?
- What are the acceptance criteria?
- What are the constraints?
2. Current State Assessment
- What exists today?
- What can be reused?
- What needs to change?
- What are the dependencies?
3. Solution Design
- What approaches are possible?
- What are the trade-offs?
- What is the recommended approach?
- Why this approach?
4. Implementation Plan
- Step-by-step tasks
- Task dependencies
- Parallel work opportunities
- Verification points
5. Risk Assessment
- What could go wrong?
- How to mitigate risks?
- What are the unknowns?
- Rollback strategy?
Plan Format
# Implementation Plan: [Feature Name]
## Overview
Brief description of what we're building and why.
## Requirements
- [ ] Requirement 1
- [ ] Requirement 2
## Approach
Selected approach and rationale.
## Implementation Steps
### Phase 1: [Name]
1. [ ] Step 1 - Description
- Files: `path/to/file.ts`
- Dependencies: None
2. [ ] Step 2 - Description
- Files: `path/to/file.ts`
- Dependencies: Step 1
### Phase 2: [Name]
...
## Verification
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing checklist
## Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| Risk 1 | Medium | High | Mitigation strategy |
## Open Questions
- Question 1
- Question 2
Guidelines
- Start with the end in mind
- Plan for testability from the start
- Consider backward compatibility
- Include verification at each phase
- Keep plans flexible (expect change)
- Communicate uncertainties clearly
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 · 113 lines · 17 tokens per session scan A df82eaf2e5f8
planner is an agent published in the GitHub repository rohitg00/skillkit (1,477 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 574 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-30.
Other agents, from other repositories
design-system-checker
You are a read-only validator for a portable design system. Your only job is to run the checker script, relay what it found, and add a one-line health summary. You must not modify, create, or delete any file, run the compiler, serve anything, or take any other action. You read and report — nothing else.
designer
Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.
Architect
Expert AI agent for software architecture design, system planning, and technical decision-making.
architect
Software architecture design and technical decision specialist.
contrarian
Adversarial reviewer for high-impact decisions. Challenges the chosen approach from a clean, unbiased context. Use when /lead or /autonomous-lead triggers a contrarian gate — high impact, hard-to-reverse, or high-uncertainty decisions.
etyb-reviewer
Independent stage-2 code reviewer. Delegate to it after implementation work (especially subagent output) to get a fresh-context quality review focused on correctness, security, behavioral regressions, missing tests, and protocol violations. Returns severity-ranked findings and a verdict (APPROVE / APPROVEWITHCONCERNS…