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 commands/hmans/beans/beans-release-notesgit clone --depth 1 https://github.com/hmans/beansWhat 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.00000 | $0.00723 |
| Opus 5 | $0.00000 | $0.00362 |
| Sonnet 5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
beans-release-notes 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 yesterday.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Release Notes
Generate release notes from commits since the last version tag and write them to .docs.local/RELEASE.md.
Instructions
-
Find the latest version tag:
git describe --tags --abbrev=0 -
Get commits since that tag:
git log <tag>..HEAD --oneline --no-merges -
Write conversational release notes to
.docs.local/RELEASE.mdfollowing this style:
Writing Style
DO NOT just list commits. Instead, write release notes that tell a story:
- Lead with what matters most - Start with a brief intro paragraph highlighting the 2-3 most impactful changes
- Group related changes - Combine multiple commits that work toward the same goal into a single, well-explained entry
- Explain the "why" - Help users understand how changes benefit them, not just what changed
- Use natural language - Write like you're telling a colleague about the release over coffee
- Highlight breaking changes prominently - These need extra attention and migration guidance
Structure
# Release Notes for vX.Y.Z
<Opening paragraph: 1-3 sentences summarizing the release theme and most exciting changes>
## Breaking Changes
<If any: explain what changed, why, and how to migrate. Be helpful, not just factual.>
## Highlights
<The 2-4 most significant improvements, with context about why they matter>
## Other Improvements
<Grouped by area (e.g., "TUI", "CLI", "Performance") with brief descriptions>
## Bug Fixes
<Notable fixes, especially ones users might have encountered>
Linking to Commits and PRs
Include links to commits or PRs so readers can dig deeper:
-
Get the GitHub repo URL:
git remote get-url origin -
Link to commits using the short hash:
Fixed TUI crash on narrow terminals ([9e32a11](https://github.com/owner/repo/commit/9e32a11)) -
Link to PRs when commits reference them (look for
(#123)in commit messages):Simplified bean linking ([#17](https://github.com/owner/repo/pull/17))
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.
- yesterday First seen · 92 lines · 0 tokens per session scan A bc6e26dc71c0
beans-release-notes is a command published in the GitHub repository hmans/beans (909 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 723 tokens. 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 commands, from other repositories
plan-sprint
Run a design sprint end to end — challenge framing, schedule, exercises, and prototype test plan.
status
Show current Craft progress — cycles, stories, backlog in a rich dashboard view.
story-archive
Move a story from a cycle back to the backlog.
overview
Codev provides three CLI tools for AI-assisted software development.
project
Manage projects inside a topic wiki. Projects are folders under output/projects/ that group related outputs (playbooks, images, code, data) with a goal captured in WHY.md.
research-l2
Executes Phases 1-3 of the L2 process of the abapwiki knowledge base on a slice: launches the abap-functional-researcher sub-agent (gap discovery + multi-source auto-research: wiki -> raw/docs -> MCP abap-fs on the system read-only -> standard knowledge), ingests gaps and evidence, and generates questionnaires for…