count

Solid

Print your own north-star row from your own record, and nothing else. Reads .claude/harness/decision-log.md, the canvas and the hook logs in this project; prints one line (decisions before the first source file, of which citing outside evidence, kills before code, sessions). Sends nothing anywhere. Opt-in; paste the line where you like or not at all.

AI & Automation 46 stars 3 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Count: your own row, from your own record Mycelium's north star is a hypothesis (dogfood DL-1177, 2026-09-07): a builder who makes at least one build-or-kill decision on evidence from outside their own head, before their project's first source file, is the builder who comes back and later says the brief changed what they built. There is no telemetry by design (PRIVACY.md). This command is the opt-in half: it reads your repository and prints one line. It writes nothing and sends nothing. ## Run ```bash python3 "${CLAUDE_PLUGIN_ROOT}/scripts/count_builder_row.py" --project-dir . ``` Output, one line plus what it means: ``` mycelium row | first source file 2026-06-02 | decisions before it 4 (of 31 dated) | citing outside evidence 2 (lexical proxy, upper bound) | kills before code 1 | sessions 12 ``` ## What the numbers are, and which are proxies - **first source file**: the first commit that added a code file outside `.claude/` and `docs/`. Without git, or before any such file, it reads `unknown` and nothing is "before" it. - **decisions before it**: dated entries in your decision log on or before that day. - **citing outside evidence**: an entry carrying a URL, an `external_*` source class, a `(per ...)` citation or an interview word. **A lexical proxy and an upper bound**: the unit asks for a person in the pipeline or a fact about the market, and a link to your own notes matches too. Read the entries if the number matters. - **kills before code**: cycle rows killed or...

Details

Author
haabe
Repository
haabe/mycelium
Created
5 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

show-your-work

Keep a reviewable decision trail for work nobody is watching: an unattended or scheduled run, a multi-phase build, a fleet of agents, or anything a human will review after stepping away. Use when starting such work, or when asked to show your work.

5 Updated today
djnsty23
AI & Automation Solid

receipts

Generate a personal Claude Code usage & impact report ("receipts") from this machine's local session transcripts — for justifying Claude Code usage/spend to a manager, self-review, or "what have I been using this for" check-ins. Mines ~/.claude/projects locally (no extra API calls beyond one final write-up), cross-references local git history, and writes a markdown report plus a self-contained HTML receipt to your home directory. Use when the user asks for "receipts", an "impact report", "usage report", wants to "show my Claude Code activity", "prove the value of Claude Code", or runs `/receipts`.

47 Updated yesterday
thevibeworks
Code & Development Listed

receipts

Generate a personal Claude Code usage & impact report ("receipts") from this machine's local session transcripts — for justifying Claude Code usage/spend to a manager, self-review, or "what have I been using this for" check-ins. Mines ~/.claude/projects locally (no extra API calls beyond one final write-up), cross-references local git history, and writes a markdown report plus a self-contained HTML receipt to your home directory. Use when the user asks for "receipts", an "impact report", "usage report", wants to "show my Claude Code activity", "prove the value of Claude Code", or runs `/receipts`.

1 Updated 1 months ago
mostwise