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/masayan1126/masayan-uni-code-pluginsWrote 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/commands/masayan1126/masayan-uni-code-plugins/plan-chrome-extension)<a href="https://agentmods.dev/commands/masayan1126/masayan-uni-code-plugins/plan-chrome-extension"><img src="https://agentmods.dev/badge/commands/masayan1126/masayan-uni-code-plugins/plan-chrome-extension/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/commands/masayan1126/masayan-uni-code-plugins/plan-chrome-extension"><img src="https://agentmods.dev/badge/commands/masayan1126/masayan-uni-code-plugins/plan-chrome-extension.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.00016 | $0.00138 |
| Opus 5.5 | $0.00006 | $0.00055 |
| Sonnet 5.5 | $0.00003 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
plan-chrome-extension 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.
What it actually says
Execute the skill at skills/chrome-extension-planning to plan and design a Chrome extension.
Read the following files to understand the workflow:
skills/chrome-extension-planning/SKILL.md- Skill overviewskills/chrome-extension-planning/WORKFLOW.md- Detailed workflowskills/chrome-extension-planning/TEMPLATES.md- Planning document templatesskills/chrome-extension-planning/BEST_PRACTICES.md- Best practices
For monetization guidance, refer to skills/common/MONETIZATION.md.
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 · 14 lines · 16 tokens per session scan A 8453fe7ccc37
plan-chrome-extension is a command published in the GitHub repository masayan1126/masayan-uni-code-plugins (5 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 138 once invoked, about $0.0001 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.