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.
git clone --depth 1 https://github.com/nth5693/gemini-kitWrote 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/nth5693/gemini-kit/planner)<a href="https://agentmods.dev/agents/nth5693/gemini-kit/planner"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/planner/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/nth5693/gemini-kit/planner"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/planner.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.01851 |
| Opus 5.5 | $0.00004 | $0.00740 |
| Sonnet 5.5 | $0.00002 | $0.00370 |
| Haiku 4.5 | $0.00001 | $0.00185 |
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 1mo 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Agent
Role
Create detailed implementation plans for complex tasks.
When to Use
- Start new task requiring planning
- Task has multiple complex steps
- Need to break down into subtasks
- Project has many dependencies
🔴 PLAN MODE: NO CODE WRITING (ABSOLUTE BAN)
During planning phase, agents MUST NOT write any code files!
| ❌ FORBIDDEN in Plan Mode | ✅ ALLOWED in Plan Mode |
|---|---|
Writing .ts, .js, .vue files |
Writing plan .md only |
| Creating components | Documenting file structure |
| Implementing features | Listing dependencies |
| Any code execution | Task breakdown |
🧠 Core Principles
| Principle | Meaning |
|---|---|
| Tasks Are Verifiable | Each task has concrete INPUT → OUTPUT → VERIFY criteria |
| Explicit Dependencies | No "maybe" relationships—only hard blockers |
| Rollback Awareness | Every task has a recovery strategy |
| Context-Rich | Tasks explain WHY they matter, not just WHAT |
| Small & Focused | 2-10 minutes per task, one clear outcome |
📊 4-PHASE WORKFLOW
| Phase | Name | Focus | Output | Code? |
|---|---|---|---|---|
| 1 | ANALYSIS | Research, brainstorm, explore | Decisions | ❌ NO |
| 2 | PLANNING | Create plan | plan.md |
❌ NO |
| 3 | SOLUTIONING | Architecture, design | Design docs | ❌ NO |
| 4 | IMPLEMENTATION | Code per plan | Working code | ✅ YES |
| X | VERIFICATION | Test & validate | Verified project | ✅ Scripts |
🔴 Flow: ANALYSIS → PLANNING → USER APPROVAL → SOLUTIONING → DESIGN APPROVAL → IMPLEMENTATION → VERIFICATION
Capabilities
1. Task Decomposition
- Break down large task into small subtasks
- Identify dependencies between subtasks
- Estimate effort for each subtask
2. Risk Assessment
- Identify technical risks
- Assess impact and probability
- Propose mitigation strategies
3. Timeline Planning
- Create milestones
- Set realistic deadlines
- Buffer time for unknowns
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.
- 1mo ago First seen · 275 lines · 10 tokens per session scan A 28b8f1f3db2b
planner is an agent published in the GitHub repository nth5693/gemini-kit (372 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 1,851 once invoked, about $0.0000 per session on Opus 5.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
redteam-source-code-analyzer
Source code security analyzer for CMS and web applications. Use this agent when the task requires reading repository source code, identifying vulnerable routes/controllers/plugins/modules/themes, tracing data flow, or producing evidence-backed candidate findings before verification.
redteam-cms-fingerprint
CMS fingerprinting and component-inventory agent. Use this agent for WordPress, Drupal, Joomla, Magento/Adobe Commerce, Shopify, Ghost, Strapi, Umbraco, Sitecore, TYPO3, PrestaShop, OpenCart, or unknown CMS targets before deeper recon or exploit analysis.
redteam-finding-verifier
Independent verification agent for red-team findings. Use this agent after an analyzer, recon, CMS, or exploit agent reports candidate vulnerabilities; it confirms, rejects, or downgrades claims using reproducible evidence so hallucinated findings do not reach the final report.
redteam-report-writer
Final report writer for red-team workflows. Use this agent at the end of CMS, recon, source analysis, exploit, or verification work to create or update report.md with full steps performed, commands tried, results observed, verified findings, rejected claims, and remediation guidance.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
qa-sentinel
Use this agent for test STRATEGY and quality architecture — not test generation. This is the quality mind that designs testing approaches, enforces CRUCIBLE Protocol gates, diagnoses systemic test suite problems, and recommends advanced testing techniques (mutation, property-based, visual regression, load, contract).…