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/anilcancakir/claude-code-plugins/my_sendgit clone --depth 1 https://github.com/anilcancakir/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/anilcancakir/claude-code-plugins/my_send)<a href="https://agentmods.dev/commands/anilcancakir/claude-code-plugins/my_send"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code-plugins/my_send.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.01728 |
| Opus 5 | $0.00009 | $0.00864 |
| Sonnet 5 | $0.00004 | $0.00346 |
| Haiku 4.5 | $0.00002 | $0.00173 |
Grade A, and why
my_send 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.
How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Send Changes Command
Complete pre-commit workflow that runs /my_review, /my_docs, and /my_commit in sequence with state tracking and intelligent flow control.
Arguments
Parse from $ARGUMENTS:
- --skip-review: Skip code review phase
- --skip-docs: Skip documentation update phase
- --quick: Run minimal checks (equivalent to --skip-review --skip-docs)
Default (no args): Full workflow with all phases.
Workflow Overview
┌─────────────────────────────────────────────────────────────┐
│ /my_send Workflow │
├─────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ Review │────▶│ Docs │────▶│ Commit │ │
│ └─────────┘ └─────────┘ └─────────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │Critical │ │ Updates │ │ Message │ │
│ │ Issues? │ │ Applied │ │Approved │ │
│ └────┬────┘ └─────────┘ └────┬────┘ │
│ │ │ │
│ Yes: │ Fix/Skip │ Yes: Push? │
│ ▼ ▼ │
│ ┌─────────┐ ┌─────────┐ │
│ │ User │ │ Done! │ │
│ │Decision │ └─────────┘ │
│ └─────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘
Execution Steps
Step 0: Initialize State
Use the workflow state management script:
# Check for existing workflow
EXISTING=$("${CLAUDE_PLUGIN_ROOT}/scripts/workflow-state.sh" check 2>/dev/null || echo "none")
if [ "$EXISTING" = "active" ]; then
# Resume existing workflow
PREV_STATE=$("${CLAUDE_PLUGIN_ROOT}/scripts/workflow-state.sh" get)
echo "Resuming previous workflow..."
else
# Initialize new workflow
"${CLAUDE_PLUGIN_ROOT}/scripts/workflow-state.sh" init
fi
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 First seen · 273 lines · 18 tokens per session scan A 17f23b464262
my_send is a command published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 1,728 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
capture
Run stackmemory capture to commit current work and generate a handoff prompt for the next session.
undo-commit
Soft-undo the last commit. Restores its changes as staged, leaves working tree intact. Refuses if HEAD is already pushed to a tracked remote.
debug
Systematic debugging with hypotheses and evidence gathering.
health
Run the Self-Star Doctor - a green/yellow/red health board across all 7 junctions of the self- loop.
plan-new
Plan a complex project with discovery, structure, and kill criteria.
create-hook
Create a new custom automation hook.