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 skills add VandanaAjayDubey111/great-pm --skill circles-methodgit clone --depth 1 https://github.com/VandanaAjayDubey111/great-pmWrote 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/skills/vandanaajaydubey111/great-pm/circles-method)<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/circles-method"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/circles-method/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/skills/vandanaajaydubey111/great-pm/circles-method"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/circles-method.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.00088 | $0.01259 |
| Opus 5.5 | $0.00035 | $0.00504 |
| Sonnet 5.5 | $0.00018 | $0.00252 |
| Haiku 4.5 | $0.00009 | $0.00126 |
Grade A, and why
circles-method 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex host binding
- Treat references to Claude slash workflows as the equivalently named Codex skill.
- Before delegating to any specialist, read the
great-pm-runtimeskill and the selected packaged role file. - Treat "invoke", "assign", "delegate", "spawn", and source Agent-tool instructions as a required Codex
spawn_agentcall with that role and a bounded assignment. - For the spawn tool's
task_nameoragent_nameidentifier, replace canonical role-name hyphens with underscores (query-refiner-pm→query_refiner_pm). Keep canonical names unchanged in prompts, filenames, verdict logs, and user-facing output; this is an internal identifier mapping, not a role rename. - Store every returned agent identifier. Never call a wait tool until a spawn has returned an identifier, and wait only on identifiers returned by successful spawns.
- If
spawn_agentis unavailable or a spawn fails, report BLOCKED; do not impersonate the specialist or wait on an empty agent set. - Resolve bundled paths from the installed GreatPM plugin root.
- Ignore Claude-only model aliases, colors, turn limits, and tool allowlists.
- Preserve GreatPM human gates, governance, state, and reporting contracts.
CIRCLES Method
A 7-step framework (Lewis C. Lin, Decode and Conquer) for answering product- design questions completely instead of jumping to a solution. The discipline is that you do not propose solutions until after you've understood the situation, named a specific customer, and prioritized their needs.
CIRCLES = Comprehend · Identify · Report · Cut · List · Evaluate · Summarize.
The seven steps
C — Comprehend the situation Clarify the question before answering. What is the product/feature? Who's asking and why now? What are the constraints (platform, timeline, business model)? What's the goal — growth, revenue, retention, a new segment? State assumptions explicitly. The classic mistake is answering a question you weren't asked.
I — Identify the customer Pick a specific customer segment. Not "everyone" — a named persona with a context. If multiple segments exist, list them, then choose ONE to design for this pass and say why (size, strategic value, acuteness of pain).
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 · 100 lines · 88 tokens per session scan A 2b70216d2f79
circles-method is a skill published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,259 once invoked, about $0.0004 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-09-21.
Other skills, from other repositories
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, UI mockups, product shots, or transparent-background cutouts. Use when the result should be an image asset rather than repo-native SVG, HTML/CSS, or canvas.
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.
bento-slides
Use when creating or editing Bento (.bento.html) slide decks, including any request for a single-file HTML slide deck.
execution-orchestrator
A planning and coordination skill for substantial coding tasks. It chooses how work should be organized, tracked, delegated, reviewed, and resumed across execution steps.
nexus-configuration
A skill for reading, planning, approving, and checking configuration in Nexus, the current private conversation or room. It covers settings such as agents, rooms, providers, channels, connectors, skills, models, tools, and MCP connections.
automation
Instructions for managing scheduled tasks through the host's structured automation tool, including reminders, delayed work, recurring checks, and result delivery.