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.
npx agentmods add commands/ruslan-korneev/claude-plugins/issue-deletegit clone --depth 1 https://github.com/ruslan-korneev/claude-pluginsWhat 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 | $0.00010 | $0.00308 |
| Opus 5 | $0.00005 | $0.00154 |
| Sonnet 5 | $0.00002 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
linear:delete 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
Command /linear:delete
Archive or permanently delete a Linear issue. Archives by default.
Instructions
Step 0: Validate Configuration
Check LINEAR_API_KEY and LINEAR_TEAM are set.
Step 1: Fetch Issue
Parse id to extract team key and number. Fetch issue to confirm it exists and get its UUID and title.
Step 2: Execute Action
If archive (default, archive is not "false"):
Use issueArchive mutation from graphql-queries.md.
If permanent delete (archive=false):
Use issueDelete mutation. This is irreversible.
Step 3: Display Result
## Issue Archived
**TEAM-123**: Issue title here
The issue has been archived and moved to the archive view.
Or for permanent delete:
## Issue Deleted
**TEAM-123**: Issue title here
The issue has been permanently deleted. This action cannot be undone.
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 First seen · 60 lines · 10 tokens per session scan A 17a6359aceae
linear:delete is a command published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 308 once invoked, about $0.0001 per session on Opus 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-08-31.
Other commands, from other repositories
create-command
Create slash commands with brainstorming and best practices.
create-hook
Create hooks with brainstorming and security-first design.
improve-skills
Identify and implement skill improvements from execution logs and user evaluations.
validate-hook
Validate hooks for security, performance, and SDK compliance.
hooks-eval
Evaluate all hooks in a plugin for quality and compliance.
evaluate-skill
Manually evaluate a recent skill execution to record qualitative feedback.