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/commentgit 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.00019 | $0.00406 |
| Opus 5 | $0.00010 | $0.00203 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
linear:comment 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:comment
Edit or delete comments on a Linear issue.
For listing and adding comments, use the Linear MCP tools (
list_comments,create_comment).
Instructions
Step 0: Validate Configuration
Check LINEAR_API_KEY and LINEAR_TEAM are set.
Step 1: Resolve Issue
Parse id to extract team key and number. Fetch issue UUID using issues query with filter.
Step 2: Execute Action
action=edit
Requires comment-id and text. Use commentUpdate mutation:
mutation CommentUpdate($id: String!, $input: CommentUpdateInput!) {
commentUpdate(id: $id, input: $input) {
success
comment {
id
body
}
}
}
Variables:
{
"id": "comment-uuid",
"input": { "body": "Updated text" }
}
Display confirmation with updated comment preview.
action=delete
Requires comment-id. Use commentDelete mutation:
mutation CommentDelete($id: String!) {
commentDelete(id: $id) {
success
}
}
Display confirmation of deletion.
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 · 81 lines · 19 tokens per session scan A 58fe186c9ab8
linear:comment is a command published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 406 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
promote-discussions
Check GitHub Discussions for highly voted learnings and promote them to Issues.
contact-upsert
Create or update a contact, optionally assign to groups.
sync
Sync the audit manifest with Azure DevOps work items — set the connector up for the first time (connect: verify the transport, report which auth path is in effect, prove access read-only, detect the board's process), push manifest bugs/tasks/phases to ADO (board states, sprint stamp, Remaining Work, comments), pull…
task
Add a tracked task to the audit manifest — every answer is a flag, and the dialogue only covers what the caller did not pass — move one between phases, or cancel work that will not be done. add allocates the id, initializes all orchestrator fields, updates fileIndex, and revalidates; move renumbers a task into another…
run
Audit pipeline: execute exactly one task by id, with status guards (done/blocked/inprogress) and blocker checks. --dry-run previews without mutating.
phase
Audit pipeline: everything a phase has done to it — add one to a plan that already exists, run it end to end (every ready task, parallel where safe, then sign-off), pin which phase the pipeline reaches for first, or cancel one that will not be done. A bare runs it; --dry-run previews the run without mutating.