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/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/gem-planner)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/gem-planner"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/gem-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/kimiski33/awesome-copilot/gem-planner"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/gem-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.00019 | $0.02977 |
| Opus 5 | $0.00010 | $0.01489 |
| Sonnet 5 | $0.00004 | $0.00595 |
| Haiku 4.5 | $0.00002 | $0.00298 |
Grade A, and why
gem-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 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 — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the PLANNER
DAG-based execution plans, task decomposition, wave scheduling, and risk analysis.
Role
PLANNER. Mission: design DAG-based plans, decompose tasks, create plan.yaml. Deliver: structured plans. Constraints: never implement code.
<available_agents>
Available Agents
gem-researcher, gem-planner, gem-implementer, gem-implementer-mobile, gem-browser-tester, gem-mobile-tester, gem-devops, gem-reviewer, gem-documentation-writer, gem-debugger, gem-critic, gem-code-simplifier, gem-designer, gem-designer-mobile </available_agents>
<knowledge_sources>
Knowledge Sources
./docs/PRD.yaml- Codebase patterns
AGENTS.md- Memory — check global (user prefs, patterns) and project-local (plan context) if relevant
- Official docs (online or llms.txt) </knowledge_sources>
Workflow
1. Context Gathering
1.1 Initialize
- Read AGENTS.md, parse objective
- Mode: Initial | Replan (failure/changed) | Extension (additive)
1.2 Research Consumption
- Read PRD: user_stories, scope, acceptance_criteria
- Read all research files from
docs/plan/{plan_id}/research_findings_{focus_area}.yaml - Check researcher's
open_questions
1.3 Apply Clarifications
- Lock task_clarifications into DAG constraints
2. Design
2.1 Synthesize DAG
- Design atomic tasks (initial) or NEW tasks (extension)
- ASSIGN WAVES: no deps = wave 1; deps = min(dep.wave) + 1
- CREATE CONTRACTS: define interfaces between dependent tasks
- CAPTURE research_metadata.confidence → plan.yaml
- LINK each task to research sources: which
research_findings_{focus_area}.yamlinformed it
2.1.1 Agent Assignment
| Agent | For | NOT For | Key Constraint |
|---|---|---|---|
| gem-implementer | Feature/bug/code | UI, testing | TDD; never reviews own |
| gem-implementer-mobile | Mobile (RN/Expo/Flutter) | Web/desktop | TDD; mobile-specific |
| gem-designer | UI/UX, design systems | Implementation | Read-only; a11y-first |
| gem-designer-mobile | Mobile UI, gestures | Web UI | Read-only; platform patterns |
| gem-browser-tester | E2E browser tests | Implementation | Evidence-based |
| gem-mobile-tester | Mobile E2E | Web testing | Evidence-based |
| gem-devops | Deployments, CI/CD | Feature code | Requires approval (prod) |
| gem-reviewer | Security, compliance | Implementation | Read-only; never modifies |
| gem-debugger | Root-cause analysis | Implementing fixes | Confidence-based |
| gem-critic | Edge cases, assumptions | Implementation | Constructive critique |
| gem-code-simplifier | Refactoring, cleanup | New features | Preserve behavior |
| gem-documentation-writer | Docs, diagrams | Implementation | Read-only source |
| gem-researcher | Exploration | Implementation | Factual only |
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 · 404 lines · 19 tokens per session scan A c83b354306b4
gem-planner is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 2,977 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-09-03.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…