Borrowing it
Nothing to install: this file belongs to zhu-kai/whodecided. 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/zhu-kai/whodecided/main/.claude/skills/add-signal/SKILL.mdgit clone --depth 1 https://github.com/zhu-kai/whodecidedWrote 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/zhu-kai/whodecided/add-signal)<a href="https://agentmods.dev/skills/zhu-kai/whodecided/add-signal"><img src="https://agentmods.dev/badge/skills/zhu-kai/whodecided/add-signal/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/zhu-kai/whodecided/add-signal"><img src="https://agentmods.dev/badge/skills/zhu-kai/whodecided/add-signal.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.00416 |
| Opus 5 | $0.00026 | $0.00208 |
| Sonnet 5 | $0.00010 | $0.00083 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
add-signal 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 12d 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
A signal is a deterministic judgement over data already on hand (ledger entries, branch diff, traces). Adding one:
-
Pure function in
src/checks/- data in, struct out, unit-tested directly. Never call git, fs, or an LLM from checks; the impure gathering lives insrc/git.tsandsrc/commands/signals.ts. -
Language rule. Ledger prose is in the user's language, so a signal must not depend on matching prose keywords. Semantics come from structured fields - if the meaning is only in the prose, add a distiller tag (
tagsinsrc/ledger/schema.ts+ the tags contract insrc/distill/prompt.ts) and match on the tag. English keyword regexes are acceptable only as a fallback for pre-tag entries. -
Wire once in
src/commands/signals.ts(analyzeBranchfor per-branch data,decisionSignalsfor per-decision) - review, board, and report all consume from there. Do not compute signals inside a command. -
Surface it:
src/render/html.ts(WorkbenchEntry field + drawer/attention/triage as fits) andsrc/render/md.tsif it belongs in the PR report. Negative/actionable signals go in the drawer's needs-attention block; healthy states stay out of the way.
Scoring conventions in checks/risk.ts: silent 35 / hard-to-reverse 25 / assumption 20; diff churn, relative churn ("rewrote N% of a file", new files excluded), and scatter (entropy) top it up. High >= 60, medium >= 32. Keep new factors proportionate.
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.
- 12d ago First seen · 17 lines · 51 tokens per session scan A 0825c0cdc380
add-signal is a skill published in the GitHub repository zhu-kai/whodecided (22 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 416 once invoked, about $0.0003 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
audit
Audit phase. Parallel review: code quality + security + tests. Semantic dedup of cross-mode findings. Outputs PASS/WARN/FAIL per dimension. Validates spec coverage.
perf
Performance optimizer for loops, DB queries, rendering, and batch operations. Catches N+1 queries, missing indexes, and unnecessary re-renders.
_critic
HarnessX Critic (Tier 2.1) — adversarial review of evolved-skill proposals against trace evidence. Detects reward hacking and manifest/evidence contradictions. Out-of-band LLM counterpart to the in-loop deterministic critic in src/evolve/critic.rs.
simplify
Code simplification for high-complexity files. Targets deep nesting, copy-paste patterns, and god functions.
toxic-senior-reviewer
Code review in the voice of a toxic senior developer — dry sarcasm without profanity, no fluff, no empty praise. Use this skill whenever the user asks for a code review, says "how can I improve this", "what do you think of this code", "take a look at this", "rate this solution", "critique this", "do a code review"…
request-review
Prepare work for review so a reviewer can verify it fast and fairly. Triggers on get this reviewed, ready for review, request a review, hand off for review.