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/thrashr888/allbeads/developmentnpx skills add thrashr888/AllBeads --skill developmentgit clone --depth 1 https://github.com/thrashr888/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/skills/thrashr888/allbeads/development)<a href="https://agentmods.dev/skills/thrashr888/allbeads/development"><img src="https://agentmods.dev/badge/skills/thrashr888/allbeads/development.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.00027 | $0.01823 |
| Opus 5 | $0.00014 | $0.00911 |
| Sonnet 5 | $0.00005 | $0.00365 |
| Haiku 4.5 | $0.00003 | $0.00182 |
Grade A, and why
development 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 4d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AllBeads Development Process Skill
Use this skill when planning features, creating documentation, tracking work with beads, or understanding how the documentation system works.
Quick Reference
Specs: specs/PRD-00.md - Core architecture specification
Issues: .beads/ - Git-tracked issue database
Plans: plans/ - Preserved plan history (git-tracked)
The 5-Style Documentation System
AllBeads uses 5 distinct doc types, each with a specific purpose:
| Style | Purpose | Location | Update Trigger |
|---|---|---|---|
| 1. Plan Mode | Deep exploration before coding | plans/ |
Per feature |
| 2. Beads Issues | Track work across sessions | .beads/ |
Throughout feature |
| 3. Evergreen Specs | System truth ("how it works") | specs/ |
Architecture changes |
| 4. Skills | Agent guides ("how to implement") | .claude/skills/ |
Pattern changes |
| 5. User Docs | Human communication | README, CLAUDE.md | Major features |
Workflow: From Idea to Code
Step 1: Enter Plan Mode
For any non-trivial feature:
1. Use EnterPlanMode tool
2. Launch Explore agents to understand existing patterns
3. Read relevant specs (specs/PRD-00.md, specs/SPEC-*.md, etc.)
4. Ask clarifying questions via AskUserQuestion
5. Design implementation approach
6. Write plan to plan file
7. Exit plan mode with ExitPlanMode for approval
8. Copy approved plan to plans/ directory (see naming below)
Plan file naming: plans/YYYY-MM-DD-feature-name.md
Example: plans/2026-01-15-external-plugins.md
Plans are preserved even if abandoned - they document design decisions and exploration history.
Step 2: Create Beads Issues
After plan approval:
# Create feature epic
bd create --title="Feature X" --type=feature --priority=2
# Break into tasks
bd create --title="Implement X logic" --type=task --priority=2
bd create --title="Add X tests" --type=task --priority=2
# Set dependencies
bd dep add <task-id> <feature-id> # Task depends on feature
# Claim work
bd update <id> --status=in_progress
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.
- 4d ago First seen · 256 lines · 27 tokens per session scan A b69dd74834f9
development is a skill published in the GitHub repository thrashr888/AllBeads (8 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 1,823 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 skills, from other repositories
c-jira
Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
stale-ticket-triage
Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.
c-linear
Manage Linear issues and projects using the linear CLI. List and filter issues, create new issues, update status, start work on a branch, and create linked pull requests directly from the terminal.
linear
Linear project management — issues, cycles, and projects via GraphQL API.
Jira Automation
Automate Jira project management workflows, sprint planning, issue tracking, and reporting.
pm-skills
Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms. Triggers on 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it…