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/writing)<a href="https://agentmods.dev/plugins/atman-33/workhub/writing"><img src="https://agentmods.dev/badge/plugins/atman-33/workhub/writing/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/plugins/atman-33/workhub/writing"><img src="https://agentmods.dev/badge/plugins/atman-33/workhub/writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
writing 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 14d 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": "writing",
"version": "0.2.1",
"description": "Write and rewrite natural Japanese work documents: a style constitution, doctype guides and readability principles for new writing, plus a meaning-preserving rewrite procedure with Node lint and diff checks for removing machine-sounding text. Install at user scope to make it available across all projects.",
"author": {
"name": "atman-33",
"url": "https://github.com/atman-33/workhub"
},
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 586 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.
- 14d ago Changed 951c31e7cb35
- 1mo ago First seen · 11 lines scan A ab6caab91c93
writing is a plugin published in the GitHub repository atman-33/workhub (3 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-13.
Other plugins, from other repositories
superbrain
Automatic Claude Code -> Obsidian second brain: zero-config session capture, hybrid search, autonomous recall, daily/lessons/preferences.
ragkit
Standalone knowledge-base RAG (vector + lexical + metadata recall, RRF-fused).
skill-fetch
Search, discover, and install AI agent skills from 9 registries with quality scoring, security labels, and cross-platform support.
expo-launchpad
Idea-to-playable harness for Expo (React Native + TypeScript) apps and games: research, plan, design, contract, and a generator-evaluator build loop with skeptical QA. --kind app|game.
dding-dong
A Claude Code notification plugin that uses sounds and operating-system alerts when work finishes, fails, or needs input.
claude-bedrock
Second Brain automation for Obsidian vaults — entity management, ingestion, compression, and sync via Claude Code skills.