Borrowing it
Nothing to install: this file belongs to hoangsonww/WealthWise-Finance-Tracker. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hoangsonww/WealthWise-Finance-Tracker/master/.agents/skills/bead-workflow/SKILL.mdgit clone --depth 1 https://github.com/hoangsonww/WealthWise-Finance-TrackerWrote 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/hoangsonww/wealthwise-finance-tracker/bead-workflow)<a href="https://agentmods.dev/skills/hoangsonww/wealthwise-finance-tracker/bead-workflow"><img src="https://agentmods.dev/badge/skills/hoangsonww/wealthwise-finance-tracker/bead-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hoangsonww/wealthwise-finance-tracker/bead-workflow"><img src="https://agentmods.dev/badge/skills/hoangsonww/wealthwise-finance-tracker/bead-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 33 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00021 | $0.00340 |
| Opus 5 | $0.00010 | $0.00170 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
bead-workflow 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 10d 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
Bead Workflow Skill
Execute the Agentic Coding Flywheel bead lifecycle.
Usage
$bead-workflow # Find and work on the next highest-leverage bead
$bead-workflow br-021 # Work on a specific bead
Process
- Find: Use
bv --robot-triageor read.beads/issues.jsonl+.beads/deps.jsonlto find unblocked beads - Claim: Mark as
in_progress, announce via Agent Mail thread[br-XXX] - Reserve: Reserve target files in
.agent-sessions/mail/reservations.jsonl - Implement: Follow bead body (Context → What to Do → Acceptance Criteria → Files to Modify)
- Review: Self-review with fresh eyes, fix bugs, run tests
- Close: Mark as closed, announce completion, release reservations
- Commit:
git commit -m "[br-XXX] <description>"then push - Next: Use
bv --robot-nextto find the next bead
Conventions
- Reference bead IDs in all commits, messages, and reservations
- Follow package-specific conventions from AGENTS.md
- Run
npx turbo test --filter=@wealthwise/<package>before closing - If bead is too large, split into sub-beads first
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.
- 10d ago First seen · 35 lines · 21 tokens per session scan A ec1bda17e0cc
bead-workflow is a skill published in the GitHub repository hoangsonww/WealthWise-Finance-Tracker (24 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 340 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
run-agent
Launch and supervise Claude Code or Codex through the CCAM Run API. Use when the user wants to start a monitored agent, select a model, approval policy, sandbox, or working directory, send a follow-up, inspect live output, resume a native session, or stop a dashboard-launched run.
sprint-summary
Summarize a sprint's worth of Claude Code activity — sessions grouped by project (cwd), per-model cost breakdown, token efficiency (cache hit rate, compaction baselines), subagent effectiveness from workflow API, velocity metrics (turncount, turndurationms), and tool diversity across the sprint.
cwd-rollup
Roll up Claude Code sessions by working directory (project) from Agent Monitor data — session count, total cost, total tokens, and last-active timestamp per cwd — so per-project activity can be compared at a glance. Use when summarizing where effort and spend went across projects.
daily-standup
Generate a daily standup summary from recent Claude Code sessions — completed work grouped by project (cwd), session costs from the pricing engine, tool invocations, error/compaction/APIError events, and turn velocity metrics from session metadata (turncount, totalturndurationms).
run-history
Inspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions. Use when finding a prior launched task, checking whether a run is still attached, reviewing start/end status, or deciding whether to resume, view, or relaunch work.
cdkd
Install cdkd and use it safely from an AWS CDK project. Use when bootstrapping, synthesizing, diffing, deploying, inspecting, rolling back, migrating, or destroying dev/test stacks with cdkd.