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 skills add ohm41321/luciazero --skill discipline-reportgit clone --depth 1 https://github.com/ohm41321/luciazeroWrote 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/ohm41321/luciazero/discipline-report)<a href="https://agentmods.dev/skills/ohm41321/luciazero/discipline-report"><img src="https://agentmods.dev/badge/skills/ohm41321/luciazero/discipline-report.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.1 | $0.00039 | $0.00329 |
| Opus 5 | $0.00019 | $0.00164 |
| Sonnet 5 | $0.00008 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
discipline-report 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 8d 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
Discipline report
Resolve the first available local CLI:
luciazero discipline [--days N] [--project PATH_OR_ID] [--json]
node <this-skill-dir>/../../bin/luciazero.js discipline [--days N] [--project PATH_OR_ID] [--json]
Use the first only when on PATH; use the second from a checkout/package. If
neither local form exists, report unavailable offline. Use npx only when
package resolution is explicitly allowed.
The command reads luciazero-stats.log, accepts current
schema-versioned JSON lines and legacy space-delimited records, ignores malformed
lines without failing, and never sends data over the network. Telemetry includes
turn/Bash wall time plus Bash, verify, and skill counts; parallel Bash intervals
are merged. Raw commands and skill names are never persisted.
Treat recorded outcomes as observations, not causes. nudge means no recognized
later verify; strict-block means its strict command was red. Explanations must
say likely unless the log records the cause.
Non-Bash remainder includes tools, hooks, scheduling, and reasoning; do not label it as model latency without another measurement.
Use --project . for this repo or another name/id as needed. Use --json for
dashboards or /retro.
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.
- 8d ago First seen · 34 lines · 39 tokens per session scan A 163c957ec83a
discipline-report is a skill published in the GitHub repository ohm41321/luciazero (5 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 329 once invoked, about $0.0002 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
tfx-goal-clarify
A prompt-formatting helper that turns a rough idea written in everyday language into one Claude Code `/goal` instruction. It organizes the desired result, how to check it, limits, and when to stop.
tfx-ship
A release workflow for publishing triflux versions through GitHub Releases, the npm package registry, and the Claude Code marketplace. It also supports version changes, dry runs, skipped tests, and no-publish runs.
tfx-interview
A question-driven workflow for turning a vague implementation request into specific requirements. It measures ambiguity—how much the goal, constraints, and success criteria are unclear—and asks questions to reduce it.
star-prompt
A setup change that adds a GitHub star request to a command-line tool's installation flow. GitHub stars are public bookmarks users can give to repositories on GitHub.
tfx-hub
A Korean-language skill for managing a TFX message hub, which is a local message bus for communication between coding agents. It supports starting, stopping, checking, and routing work through the hub.
tfx-prune
A cleanup workflow that asks three AI coding assistants to independently identify unnecessary code, then removes only issues they agree are unwanted. It checks for duplication, needless abstractions, excessive error handling, and similar readability problems.