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/billbuchanan-code/claude-code-power-setup/flow.memorynpx skills add billbuchanan-code/claude-code-power-setup --skill flow.memorygit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWhat 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.00028 | $0.03480 |
| Opus 5 | $0.00014 | $0.01740 |
| Sonnet 5 | $0.00006 | $0.00696 |
| Haiku 4.5 | $0.00003 | $0.00348 |
Grade C, and why
flow.memory scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .specify/archive/NNNN-*/ How it starts
The opening of the file, as written. The whole thing — 477 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Arguments
| Argument | Description |
|---|---|
| (empty) | Run full verification with reconciliation |
--dry-run |
Analyze only, no changes |
--fix |
Auto-fix issues without confirmation |
--no-reconcile |
Skip ROADMAP/codebase checks (faster) |
--promote |
Scan completed specs for decisions to promote |
--deep |
Full codebase pattern scan (slower) |
--archive <phase|all> |
Review archived phase(s) for memory promotion |
--archive <phase|all> --delete |
Review AND delete archives after promotion |
Prerequisites
Must be on clean main branch:
# Verify: on main, no uncommitted changes, synced with origin
git rev-parse --abbrev-ref HEAD # must be "main"
git diff --quiet && git diff --cached --quiet # must be clean
git fetch origin main && [ "$(git rev-parse HEAD)" = "$(git rev-parse origin/main)" ]
Abort with specific error if any check fails.
Execution
1. Initialize
specflow status --json
specflow check --gate memory
Parse status for:
context.hasMemory→ must be true (abort if false)context.hasRoadmap→ needed for reconciliation
If memory gate fails, report specific issues from the check output.
2. Inventory Memory Documents
Scan .specify/memory/:
| Document | Status | Purpose |
|---|---|---|
constitution.md |
REQUIRED | Project principles |
tech-stack.md |
Recommended | Approved technologies |
coding-standards.md |
Recommended | Code conventions |
api-standards.md |
Recommended | API patterns |
security-checklist.md |
Recommended | Security requirements |
testing-strategy.md |
Recommended | Test patterns |
glossary.md |
Optional | Domain terms |
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 · 477 lines · 28 tokens per session scan C 1b52be799614
flow.memory is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 3,480 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
creating-skills
Guide for creating Claude Code skills following Anthropic's official best practices. Use when user wants to create a new skill, build a skill, write SKILL.md, update an existing skill, or needs skill creation guidelines. Provides structure, frontmatter fields, naming conventions, and new features like dynamic context…