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/motlin/claude-code-pluginsWrote 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/motlin/claude-code-plugins/markdown-tasks)<a href="https://agentmods.dev/plugins/motlin/claude-code-plugins/markdown-tasks"><img src="https://agentmods.dev/badge/plugins/motlin/claude-code-plugins/markdown-tasks/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/motlin/claude-code-plugins/markdown-tasks"><img src="https://agentmods.dev/badge/plugins/motlin/claude-code-plugins/markdown-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
markdown-tasks 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 3d 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
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "markdown-tasks",
"description": "Task management system using markdown checkboxes in .llm/todo.md with skills for planning, implementing, and tracking tasks across git worktrees",
"version": "1.37.0",
"license": "Apache-2.0",
"author": {
"name": "Craig Motlin"
},
"skills": ["./skills/tasks"]
}
What it installs
The manifest is a name and a version. 8 skills travel with it, and installing the plugin installs all of them — 336 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.
- 3d ago Changed 836b0d735147
- 6d ago Changed 375adb04f3a1
- 9d ago Changed f145332940b4
- 22d ago Changed · -2 lines afee5ed9453b
- 29d ago Changed 7c8e0c2efa95
- 1mo ago Changed · -7 lines c2ec569a8196
- 1mo ago Changed · -1 lines 4abf7941e717
- 1mo ago Changed 184f5fb9476a
- 1mo ago Changed ec389c43bfe6
- 1mo ago First seen · 22 lines scan A fcbc429cec88
markdown-tasks is a plugin published in the GitHub repository motlin/claude-code-plugins (20 stars, last pushed yesterday), licensed Apache-2.0. 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-04.
Other plugins, from other repositories
fuse-rules
Global rules for all Claude Code sessions: APEX workflow, SOLID/DRY enforcement, project detection, agent delegation, frontend/git standards.
lanes-bridges
Bridge Lanes with GitHub and Linear: import issues, batch-spawn a session per ticket, and post results back upstream. Split out of lanes-desktop in 0.7.0.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
gh-cli
GitHub CLI integration with focused skills for pull requests, stacked pull requests, issues, GitHub Actions, and viewing GitHub file URLs.
tgc-skills
A shipping pipeline for Claude Code: orchestrate a locked plan with fresh-context agents, polish the diff, ship it to a reviewed PR, run an agent review-fix loop until clean, and clean up after merge.
github
Drive PRs to merge-ready with gh: fix CI and review-bot feedback, plus bulk merge, close, and label.