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 agentmods add skills/bigduu/bamboo-agent/plannpx skills add bigduu/Bamboo-agent --skill plangit clone --depth 1 https://github.com/bigduu/Bamboo-agentWrote 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/bigduu/bamboo-agent/plan)<a href="https://agentmods.dev/skills/bigduu/bamboo-agent/plan"><img src="https://agentmods.dev/badge/skills/bigduu/bamboo-agent/plan.svg" alt="Measured on agentmods" 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 | $0.00068 | $0.00261 |
| Opus 5 | $0.00034 | $0.00130 |
| Sonnet 5 | $0.00014 | $0.00052 |
| Haiku 4.5 | $0.00007 | $0.00026 |
Grade A, and why
plan 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 5d 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
Plan
Explore without modifying files or external state.
- Define the desired outcome, scope, non-goals, and acceptance criteria from the request.
- Inspect repository instructions, current implementation, tests, interfaces, and related work. Resolve inexpensive factual unknowns from source before asking questions.
- Identify dependencies, sequencing constraints, compatibility boundaries, data migrations, permissions, and rollout or rollback needs.
- Produce ordered, implementation-ready steps. Name concrete files or components, describe the contract changed at each step, and attach verification to the step that creates the risk.
- Call out assumptions, open decisions, and failure modes. Ask only when a missing decision would materially change the plan.
Do not edit code, claim implementation is complete, or turn the plan into hidden execution. If tools or permissions limit exploration, mark affected steps as provisional. Preserve the outcome, constraints, decisions, and remaining questions across context compaction.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 17 lines · 68 tokens per session scan A 064bc428e47d
plan is a skill published in the GitHub repository bigduu/Bamboo-agent (16 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 261 once invoked, about $0.0003 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
release
Prepare and publish stable Agent Lightning releases through the repository's version bump, pull-request checks, merge, tag, PyPI trusted-publishing, and versioned-documentation workflows. Use when asked to plan, cut, verify, or explain a release; treat nightly TestPyPI builds as a separate path.
agent-lightning
Provides the action space, tradeoffs, and evaluation context for improving an editable AI agent against a benchmark while preserving its deployment contract. Use when optimizing agent accuracy, cost, latency, or reliability.
agentfield-use
Whenever you have a discrete task to perform — one the user delegated, or one that arose inside your own work — check FIRST whether an installed AgentField agent covers it, and offload to it by default when one does. Coverage, not task size, is the test: even a small job goes to a covering agent. The check is cheap …
agentfield
Design and ship a multi-agent system on AgentField. Use when the user asks to build, scaffold, design, or run an agent, reasoner network, multi-agent backend, or 'an agent that does X' — whenever the work would otherwise be a single LLM call or a flat LangChain/CrewAI/AutoGen chain. The skill produces composite…
agentfield-personal
Build and install a personal AI agent on this machine's AgentField: real source in /agentfield-agents, packaged with agentfield-package.yaml, installed with af install, started with af run, registered on the local control plane, and visible in AgentField Desktop with a keys form and an auto-start toggle. Use when the…
penguin-harness-dev
Use when developing PenguinHarness itself — changing packages/{core,server,web,cli,desktop,landing,docs,skills}, the built-in model catalog, the installers or the release workflow; writing or auditing changelog entries; writing a blog post or capturing release screenshots; deciding what to do about data already on…