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 rp1-run/rp1 --skill strategizegit clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/rp1-run/rp1/strategize)<a href="https://agentmods.dev/skills/rp1-run/rp1/strategize"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/strategize/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/rp1-run/rp1/strategize"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/strategize.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.00029 | $0.00360 |
| Opus 5 | $0.00015 | $0.00180 |
| Sonnet 5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
strategize 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 10d 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
Strategic Technical Advisor
This command invokes the strategic-advisor sub-agent for holistic optimization and trade-off analysis.
Directory Resolution
Use the pre-resolved kbRoot from the generated Resolve Arguments section. Pass it as {kbRoot} in the dispatch block below.
Dispatch
Invoke the strategic-advisor agent with the user's problem statement and resolved KB path:
{% dispatch_agent "rp1-base:strategic-advisor" %} PROBLEM_STATEMENT={PROBLEM_STATEMENT}, KB_ROOT={kbRoot} {% enddispatch_agent %}
The agent will:
- Analyze system comprehensively (architecture, code, usage, costs)
- Identify optimization opportunities
- Evaluate trade-offs across cost, quality, performance, complexity
- Provide quantified recommendations with ROI estimates
- Prioritize by impact and effort
- Generate detailed strategy report
- Report back with actionable recommendations
The agent has access to all necessary tools and will handle the entire strategic analysis workflow autonomously.
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.
- 10d ago First seen · 51 lines · 29 tokens per session scan A a66fcb52c6ec
strategize is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 2d ago), licensed Apache-2.0. It adds 29 tokens to every session and 360 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 skills, from other repositories
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.
brainstorm
Explore ambiguous or early-stage ideas interactively — tracks wish-readiness and crystallizes into a design for wish.
refactor-advisor
A code review helper that finds common design and maintenance problems in a codebase and suggests ways to restructure the code.
acceptance-test-authoring
Use when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an acceptance stack, or implementing OpenSpec tasks that involve acceptance tests.
spec-as-source
Use when a user or project explicitly adopts OpenSpec spec-as-source, fenced Gherkin specifications as executable acceptance tests, or acceptance-test-first OpenSpec tasks.