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/ThrownLemon/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/commands/thrownlemon/claude-code-plugins/read)<a href="https://agentmods.dev/commands/thrownlemon/claude-code-plugins/read"><img src="https://agentmods.dev/badge/commands/thrownlemon/claude-code-plugins/read/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/commands/thrownlemon/claude-code-plugins/read"><img src="https://agentmods.dev/badge/commands/thrownlemon/claude-code-plugins/read.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.00000 | $0.00579 |
| Opus 5.5 | $0.00000 | $0.00232 |
| Sonnet 5.5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade C, and why
read scanned grade C with 1 finding 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
1. **Reject dangerous tokens.** If a value contains `$(`, backticks, `;`, `|`, `&`, `>`, `<`, or starts with `-` (could be mistaken for a flag), refuse and ask the user to rephrase. **Double-quoting does NOT block comman What it actually says
Input Safety — apply before any Bash invocation
Treat every $ARGUMENTS.* value as untrusted input. Before passing any value to the Bash tool:
- Reject dangerous tokens. If a value contains
$(, backticks,;,|,&,>,<, or starts with-(could be mistaken for a flag), refuse and ask the user to rephrase. Double-quoting does NOT block command substitution —"$(rm -rf /)"still executes inside double quotes. - Prefer the Bash tool's argv contract over constructed shell strings. When you must use a shell string, single-quote the value and escape embedded single quotes (
'\''), or build the command viaprintf %q. - Any
"$ARGUMENTS.foo"patterns shown below are illustrative. Sanitize the value first; never blindly substitute.
Read Gmail Thread
View the complete contents of an email thread including all messages and attachments.
What This Does
This command delegates to the gmail-assistant subagent which will:
-
Fetch Thread
- Retrieve thread by ID
- Show all messages in conversation order
-
Display Content
- Show sender, recipients, date for each message
- Display full message body
- List any attachments
-
Attachment Handling
- List attachments with file names and sizes
- Optionally download to ~/.gmcli/attachments/
Getting Thread IDs
Thread IDs are returned from /gmcli:search. Example workflow:
/gmcli:search --query "from:alice"
# Returns: Thread 18abc123... "Meeting tomorrow"
/gmcli:read --thread 18abc123
Examples
/gmcli:read --thread 18abc123def456
/gmcli:read --thread 18abc123def456 --download true
/gmcli:read --thread 18abc123def456 --account [email protected]
Use the gmail-assistant subagent to read the thread. Pass the arguments:
- thread: $ARGUMENTS.thread
- account: $ARGUMENTS.account (optional)
- download: $ARGUMENTS.download or false
- action: read
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.
- 1mo ago First seen · 71 lines · 0 tokens per session scan C e68cae2fccfa
read is a command published in the GitHub repository ThrownLemon/claude-code-plugins (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 579 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.