Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add cboone/agent-harness-plugins/plugin install publish-report-boardWrote 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/cboone/agent-harness-plugins/publish-report-board)<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/publish-report-board"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/publish-report-board/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/cboone/agent-harness-plugins/publish-report-board"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/publish-report-board.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.00037 | $0.04081 |
| Opus 5.5 | $0.00015 | $0.01632 |
| Sonnet 5.5 | $0.00007 | $0.00816 |
| Haiku 4.5 | $0.00004 | $0.00408 |
Grade A, and why
publish-report-board 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 5d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish Report Board
Publish an analysis as a report board, and re-sync it in place when its source data changes.
A report board is an analysis with three properties that terminal output serves badly: it is re-run against source data that keeps changing, it is scanned for what to do next rather than read top to bottom, and it stays open as a working surface. Each board type is a fixed page template plus a reference describing the data it needs and how to derive it.
A board renders the source of truth and never becomes one. GitHub, or whatever else a board reads, stays authoritative, and every sync re-derives the board from it. The page holds nothing a later sync would contradict: no checkboxes, no editable status, no runtime state, and no page that saves its own versions, which would also conflict with every republish.
Board Types
| Board type | Answers | Reference |
|---|---|---|
backlog-triage |
What to start next, what can run in parallel, and what is blocked | ./references/board-types/backlog-triage.md |
bugs |
Which of a repository's bugs are critical, which are high priority, and how the rest are triaged | ./references/board-types/bugs.md |
Only these two ship a template. When the user wants a board for another kind of analysis, such as CI health or release readiness, say that no template exists for it yet and deliver the analysis in the terminal. When the user asks for a page all the same, lay it out by hand from the starter page, as Hand-Laid Reports describes. Never improvise a page from scratch or from a copy of a published one: boards read as one system because they share one design, described in ./references/design-conventions.md.
What ships with it
7 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.
- 5d ago Changed · +16 lines 2297b4e81e5b
- 8d ago Changed · +11 lines · -1 tokens per session ee7c812cbf89
- 25d ago Changed 71c04a91a17c
- 26d ago Changed · -7 lines · -102 tokens per session f30004a5895a
- 1mo ago First seen · 149 lines · 140 tokens per session scan A e442f9ea2cf2
publish-report-board is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 4,081 once invoked, about $0.0001 per session on Opus 5.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-09-13.
Other skills, from other repositories
linear-app-setup
Create and configure a Linear agent app so the assistant can manage issues, projects, and workflows under its own identity.
factory-mcp
Use the Warp Factory MCP to hand work to a software factory and collaborate with it — bundle local work and send it to the cloud, find factory tasks from a Slack thread / Linear ticket / description, and pull a task down to test or iterate locally and hand it back.
oz-notify-user
Send a progress notification to the user who triggered this Oz task (e.g., via Slack or Linear).
oz-finish-task
Report task completion or failure back to the Oz platform when done with a task.
todoist-cli
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
model-triage
Adopt the per-issue model-selection convention in a repo — tier every open issue, apply the model: labels, board field, and callouts behind an approval gate. Also runs in maintenance mode to sweep up unlabeled issues and label/field drift.