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 dailyaiagents-cpu/dailyai-os --skill receipt-stream-publishergit clone --depth 1 https://github.com/dailyaiagents-cpu/dailyai-osWrote 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/dailyaiagents-cpu/dailyai-os/receipt-stream-publisher)<a href="https://agentmods.dev/skills/dailyaiagents-cpu/dailyai-os/receipt-stream-publisher"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/receipt-stream-publisher/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/dailyaiagents-cpu/dailyai-os/receipt-stream-publisher"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/receipt-stream-publisher.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.00081 | $0.00989 |
| Opus 5 | $0.00041 | $0.00495 |
| Sonnet 5 | $0.00016 | $0.00198 |
| Haiku 4.5 | $0.00008 | $0.00099 |
Grade A, and why
receipt-stream-publisher 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
receipt-stream-publisher
The thesis: prospects don't trust marketing pages. They trust receipts. A live operational ticker showing what's shipping right now — commits, gates, smoke-tests, substrate state — is more credible than any sales page. And it's autonomous: the system documents itself in real time.
Procedure
bash skills/receipt-stream-publisher/run.sh # full hourly publish
bash skills/receipt-stream-publisher/run.sh --dry-run # build the payload, don't write
Pipeline
- Last 24h commits —
git log --since="24 hours ago" --pretty=format:'%h %s'subjects only, scrubber-checked. - Voice-gate counts — grep
voice_gate.log(if exists) for last-24h pass/fail. If no log, count = 0/0 with a "no telemetry yet" footnote. - P-gate catches — grep
data/decisions/cont-*-*.mdfor "P-gates triggered" sections in last 24h, count by gate id. - Smoke-tests — grep
logs/*.loganddata/decisions/*.mdforsmoke-test|smoke test|STATUS=okpatterns last 24h, count by skill name. - Substrate state —
bash skills/gateway-pulse/check.shandbash skills/launchd-drift-recovery/check.sh, normalize tooperational | degraded | down. - 12 P-gates active — static count from
docs/build-prompt-checklist.md. - Scrubber HARD on the assembled JSON-text-fields. If any string fails
scrubber, the whole publish aborts and writes a
STATUS=blockedtologs/receipt-stream-stderr.log. - Atomic write:
site/api/receipts.json(.tmp+ rename), then rendersite/receipts.htmlfrom a static template that reads the JSON via relative-path fetch on page load (no rebuild on JSON-only change).
Status codes
STATUS=ok json=<path> html=<path> /
STATUS=blocked reason=scrubber-fail field=<...> /
STATUS=error reason=<...>
Output schema (receipts.json)
{
"as_of": "2026-05-06T01:00:00Z",
"window_hours": 24,
"commits_24h": [{"sha": "...", "subject": "..."}, ...],
"voice_gate_24h": {"pass": 0, "fail": 0},
"p_gate_catches_24h": {"P8": 1, "P10": 1},
"smoke_passes_24h": {"heartbeat-silence-check": 5, "gateway-pulse": 24},
"substrate": {"hermes": "ok", "openclaw": "ok", "obsidian": "ok", "paperclip": "ok", "drift": "GREEN"},
"p_gates_active": 12,
"_meta": {"generator": "receipt-stream-publisher", "hour_id": "<YYYY-MM-DDTHH>"}
}
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 80 lines · 81 tokens per session scan A 72b5767b4f83
receipt-stream-publisher is a skill published in the GitHub repository dailyaiagents-cpu/dailyai-os (0 stars, last pushed 4mo ago), licensed MIT. It adds 81 tokens to every session and 989 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…