Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add thrashr888/AllBeads/plugin install allbeadsWrote 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/commands/thrashr888/allbeads/context-new)<a href="https://agentmods.dev/commands/thrashr888/allbeads/context-new"><img src="https://agentmods.dev/badge/commands/thrashr888/allbeads/context-new.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.00013 | $0.01020 |
| Opus 5 | $0.00006 | $0.00510 |
| Sonnet 5 | $0.00003 | $0.00204 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
context-new 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a brand new GitHub repository and set it up with AllBeads from the start.
This command provides a streamlined workflow similar to GitHub's "New Repository" form but adds:
- Automatic beads initialization
- AI agent configuration (CLAUDE.md, .cursorrules, etc.)
- Automatic addition to AllBeads contexts
Usage:
# Interactive mode (recommended for first-time use)
ab context new
# With arguments
ab context new myproject --private --description "My new project"
# Non-interactive mode
ab context new myproject --non-interactive --private
# Full specification
ab context new myproject \
--private \
--description "Project description" \
--license MIT \
--gitignore Rust \
--init-agents claude,cursor
Options:
| Option | Description |
|---|---|
--description |
Repository description |
--private |
Create as private repository |
--org <ORG> |
Create in an organization |
--gitignore <TEMPLATE> |
.gitignore template (Rust, Node, Python, Go, etc.) |
--license <LICENSE> |
License (MIT, Apache-2.0, GPL-3.0, etc.) |
--init-agents <LIST> |
Comma-separated agents to configure (default: claude) |
--path <PATH> |
Custom local clone path |
--no-clone |
Create on GitHub only, don't clone locally |
--wizard |
Use interactive TUI wizard |
--non-interactive |
Use defaults without prompts |
Workflow:
- Input Collection - Name, visibility, description via prompts or CLI args
- GitHub Creation - Creates repository using
ghCLI - Clone - Clones repository to local workspace
- Beads Init - Runs
bd initto set up issue tracking - Agent Config - Creates CLAUDE.md and other agent files
- Git Push - Commits and pushes configuration
- Context Add - Adds to AllBeads config
Requirements:
- GitHub CLI (
gh) must be installed and authenticated - Run
gh auth loginif not already authenticated - Token needs
reposcope for repository creation
Example Session:
$ ab context new
Create a new repository
Repository name: my-awesome-project
Description (optional): A new project with AllBeads
Private repository? [Y/n]: n
Organization (leave empty for personal account):
Common .gitignore templates: Rust, Node, Python, Go, Java
.gitignore template: Rust
Common licenses: MIT, Apache-2.0, GPL-3.0, BSD-3-Clause
License: MIT
AllBeads Configuration
Initialize beads? [Y/n]: y
Available agents: claude, cursor, copilot, aider
Agents to configure (comma-separated) [claude]: claude,cursor
Summary
Name: my-awesome-project
Visibility: Public
.gitignore: Rust
License: MIT
Beads: Yes
Agents: claude, cursor
Create repository? [Y/n]: y
Creating repository on GitHub...
✓ Created https://github.com/thrashr888/my-awesome-project
→ Cloning to /Users/me/Workspace/my-awesome-project...
✓ Cloned to /Users/me/Workspace/my-awesome-project
→ Initializing beads...
✓ Beads initialized
→ Configuring agents...
✓ Configured: claude, cursor
→ Committing configuration...
✓ Pushed to GitHub
✓ Added context 'my-awesome-project' to AllBeads config
Repository Created Successfully
Name: my-awesome-project
URL: https://github.com/thrashr888/my-awesome-project
Path: /Users/me/Workspace/my-awesome-project
Beads: initialized
Agents: claude, cursor
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 · 136 lines · 13 tokens per session scan A 93f1d3dfbdf1
context-new is a command published in the GitHub repository thrashr888/AllBeads (8 stars, last pushed 8d ago), licensed MIT. It adds 13 tokens to every session and 1,020 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-31.
Other commands, from other repositories
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
ship
Encodes the "stage and commit" ritual: verify (receipt gate) → scope → branch → write the commit message from what is actually staged → commit → push → open PR to the default branch → move the Jira issue to In Review. NO merge (merging is the reviewer's call). NO tag (deploys are project-specific and out of scope).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
next
Suggest the most likely next workflow action based on current context.
weekly-summary
Generate weekly work summary from git activity.