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 bigduu/Bamboo-agent --skill hello-worldgit 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/hello-world)<a href="https://agentmods.dev/skills/bigduu/bamboo-agent/hello-world"><img src="https://agentmods.dev/badge/skills/bigduu/bamboo-agent/hello-world.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.1 | $0.00027 | $0.00200 |
| Opus 5 | $0.00014 | $0.00100 |
| Sonnet 5 | $0.00005 | $0.00040 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
hello-world 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 7d 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
Hello World
This is a trivial skill bundled inside the hello-plugin example plugin
(crates/infra/bamboo-plugin/examples/hello-plugin/). It exists purely to
exercise the plugin system's schema end-to-end:
plugin.jsondeclares it underprovides.skillsas"hello-world".- Once the plugin is installed to
~/.bamboo/plugins/hello-plugin/, this skill is discovered in place — no copy, no symlink — because~/.bamboo/plugins/hello-plugin/skillsbecomes an additional skill discovery directory (seebamboo-skills'SkillDirectorySource::Plugin).
When invoked, just greet the user and mention that you are the example skill
from the hello-plugin plugin.
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.
- 7d ago First seen · 20 lines · 27 tokens per session scan A d4e1f6a4ad7b
hello-world is a skill published in the GitHub repository bigduu/Bamboo-agent (16 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 200 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
benchmark-design
Design and calibrate a multi-Case capability Benchmark and establish a traceable Formal Baseline.
agent-optimization
Improve an Agent State through versioned scores and score-linked Traces from a frozen Benchmark.
agent-evaluation
Run one specified Test Agent on one specified Benchmark Case exactly once, privately score that execution, and return one protocol result.
Skill: Verify skill
Skill for opinionated verification workflow for validating code changes.
install-verification
Use when verifying that a generated agent package can be installed, discovered by runtimes, and checked without private dependencies.
verify-changes
Verify code changes by running the project's typecheck, build, lint, and targeted tests, then fix and re-run until clean. Use after editing any source file.