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.
git clone --depth 1 https://github.com/atman-33/workhubWrote 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/plugins/atman-33/workhub/authoring)<a href="https://agentmods.dev/plugins/atman-33/workhub/authoring"><img src="https://agentmods.dev/badge/plugins/atman-33/workhub/authoring.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
authoring 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 2d 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
{
"name": "authoring",
"version": "0.2.0",
"description": "Author text deliverables and deliver them: README / CLAUDE.md / release notes / work logs, and posting the result to Slack. Visual deliverables — slide decks, HTML documents and PDF export — live in the visuals plugin. Install at user scope to make it available across all projects.",
"author": {
"name": "atman-33",
"url": "https://github.com/atman-33"
}
}
What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 279 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2d ago Changed 6675b5b241f0
- 3d ago First seen · 10 lines scan A 2b42f8defd63
authoring is a plugin published in the GitHub repository atman-33/workhub (2 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.
Other plugins, from other repositories
i-have-adhd
Shape Claude Code output for an ADHD reader: lead with the next action, number steps, suppress tangents, restate state, make wins visible.
iterm2-tab-status
Show iTerm2 tab status (running/idle/attention) for Claude Code sessions.
iterm-notify
macOS desktop notifications and iTerm2 badge management for Claude Code lifecycle events.
cc-notify-hooks
A notification plugin for coding agents such as Claude Code, Codex, DeepSeek Harness, and Reasonix. It sends short waiting updates through several notification channels and handles longer updates asynchronously.
i-have-adhd
Shape Gemini CLI output for an ADHD reader: lead with the next action, number steps, suppress tangents, restate state, make wins visible.
claude-timestamp
Stamps every message with the local time and how long the turn took, names the tool behind a slow turn, and reports where a session's time actually went. Claude receives the send time of each prompt, so it can reason about when things happened.