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/existential-birds/beagle/releasegit clone --depth 1 https://github.com/existential-birds/beagleWhat 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.00012 | $0.02269 |
| Opus 5 | $0.00006 | $0.01135 |
| Sonnet 5 | $0.00002 | $0.00454 |
| Haiku 4.5 | $0.00001 | $0.00227 |
Grade A, and why
release 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Automation
Automate the full release process: generate notes, update files, create branch, and open PR.
No arguments required - automatically detects the previous tag.
Versioning Overview
Beagle has two version locations:
- marketplace.json metadata.version (
.claude-plugin/marketplace.json) - Main release version, matches repo tags - Per-plugin plugin.json version (
plugins/<name>/.claude-plugin/plugin.json) - Individual plugin versions, bumped when that plugin's files change
Prerequisites
Verify we're on main and it's clean:
git checkout main
git pull
git status --short
If there are uncommitted changes, abort and ask the user to resolve them first.
Detect the previous tag:
PREV_TAG=$(git describe --tags --abbrev=0 2>/dev/null)
if [ -z "$PREV_TAG" ]; then
echo "No previous tags found. This appears to be the first release."
PREV_TAG="HEAD~100" # Fallback to analyze recent history
fi
echo "Previous tag: $PREV_TAG"
Step 1: Check for CHANGELOG.md
If CHANGELOG.md does not exist, create it with the standard header:
# Changelog
All notable changes to Beagle are documented here.
Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Versioning adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
Step 2: Verify Documentation Coverage
Before generating release notes, verify all commands and skills are documented in README.md.
Check commands coverage:
# List actual commands (excluding llm-judge which may be experimental)
COMMANDS=$(ls -1 commands/*.md 2>/dev/null | xargs -I {} basename {} .md | sort)
echo "Actual commands:"
echo "$COMMANDS"
# Commands documented in README
echo ""
echo "Commands in README:"
grep -E '^\| `[a-z-]+' README.md | sed 's/| `\([^`]*\)`.*/\1/' | sort
Check skills coverage:
# List actual skill directories
SKILLS=$(ls -1d skills/*/SKILL.md 2>/dev/null | xargs -I {} dirname {} | xargs -I {} basename {} | sort)
echo "Actual skills count: $(echo "$SKILLS" | wc -l | tr -d ' ')"
# Skills should be grouped in README by category, verify major categories exist
echo ""
echo "Skills categories in README:"
grep -E '^\| \*\*' README.md | head -10
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.
- 2d ago First seen · 247 lines · 12 tokens per session scan A 9ba4383807b7
release is a command published in the GitHub repository existential-birds/beagle (79 stars, last pushed 23d ago), licensed Apache-2.0. It adds 12 tokens to every session and 2,269 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 commands, from other repositories
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
language
Command "language" from ErisPulse/ErisPulse, covering erispulse.cli.commands.language 模块, 模块概述, 类列表 and class languagecommand(command).
run-engine-tests
Fast local test loop for the engine package.