Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Sassy-Dog/sassydog-skills/plugin install sassy-dogWrote 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/skills/sassy-dog/sassydog-skills/send-it)<a href="https://agentmods.dev/skills/sassy-dog/sassydog-skills/send-it"><img src="https://agentmods.dev/badge/skills/sassy-dog/sassydog-skills/send-it/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/skills/sassy-dog/sassydog-skills/send-it"><img src="https://agentmods.dev/badge/skills/sassy-dog/sassydog-skills/send-it.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.00100 | $0.06316 |
| Opus 5 | $0.00050 | $0.03158 |
| Sonnet 5 | $0.00020 | $0.01263 |
| Haiku 4.5 | $0.00010 | $0.00632 |
Grade A, and why
send-it scanned grade A 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 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
!`root="$(git rev-parse --show-toplevel 2>/dev/null)"; echo "CONFIG_SOURCE: ${root:-<not a git repo>}"; cat "$root/.claude/sassy-dog/send-it.md" 2>/dev/null || echo "NO_CONFIG"` Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Send-It
End-to-end PR flow, in order: worktree audit → freshness gates → pre-flight guardrails → PR body →
commit/push → watch + merge (delegated to sassy-dog:pr-shepherd).
1. Repo config
!root="$(git rev-parse --show-toplevel 2>/dev/null)"; echo "CONFIG_SOURCE: ${root:-<not a git repo>}"; cat "$root/.claude/sassy-dog/send-it.md" 2>/dev/null || echo "NO_CONFIG"
Check CONFIG_SOURCE before using any of this. It is the repo root resolved from the
session's working directory at skill-load time — not necessarily the repo you are about to act
on — and cwd resets between Bash calls, so you cannot influence it. If it names a repo other than
the one you are working in, discard the block above, read that repo's own
.claude/sassy-dog/send-it.md by absolute path, and use that instead. Config is meant to be applied
exactly as written, so the wrong one silently applies another repo's rules: on 2026-08-18 two agents
shipping in sassydog-routines and sassydog-skills were each handed platform's Terraform gates,
and caught it only by noticing the mismatch themselves.
Frontmatter supplies preflight_commands, pr_template_path, pr_template_sections,
merge_queue, and the optional migrations, codegen, and stacked_prs blocks. review_agent:
is optional too, but its absence is not an off switch — it selects the shipped
sassy-dog:pr-review-orchestrator (§4), which an optional review_surfaces: map may steer.
Contract: sassy-dog:setup-config → references/config-contract.md.
Repo slug and default branch are derived, never configured:
gh repo view --json nameWithOwner,defaultBranchRef \
--jq '"repo=\(.nameWithOwner) branch=\(.defaultBranchRef.name)"'
If it reads NO_CONFIG
Run §2 — the worktree audit is universal and never skipped. Then stop before pushing and say so:
No
.claude/sassy-dog/send-it.mdin this repo. I can audit the worktree and draft the commit, but I don't know this repo's pre-flight commands or PR template. If this repo has a project-levelsend-itunder.claude/skills/, use that instead. Otherwise: tell me the pre-flight command, or runsassy-dog:setup-config.
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 Changed · +70 lines 3a6359ef712a
- 6d ago Changed · +1 lines 4acb1a3a988d
- 10d ago First seen · 370 lines · 100 tokens per session scan A f9cb5d6a33f6
send-it is a skill published in the GitHub repository Sassy-Dog/sassydog-skills (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 100 tokens to every session and 6,316 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
update-pr
Update an existing pull request with new changes. Use when the user wants to update a PR, push follow-up changes to a PR, refresh a PR description, or sync a PR with latest commits. Triggers on: update pr, update-pr, update the pr, push to pr, refresh pr, sync pr, update pull request.
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
merge-prep
Pre-merge analysis and preparation. Analyzes source branch vs target branch: commit stats, conflict detection, file impact. Analysis-only v1 — outputs report + suggested commands, does not auto-merge. Use when: user says 'merge prep', 'pre-merge', 'merge analysis', or /merge-prep.