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/coltonbearden/carrelWrote 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/coltonbearden/carrel/sign)<a href="https://agentmods.dev/commands/coltonbearden/carrel/sign"><img src="https://agentmods.dev/badge/commands/coltonbearden/carrel/sign.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.1 | $0.00034 | $0.01017 |
| Opus 5 | $0.00017 | $0.00508 |
| Sonnet 5 | $0.00007 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
sign 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 yesterday.
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
Handle this signing request: $ARGUMENTS
Run the carrel CLI via Bash. carrel sign is a group with stamp, manifest and verify; map the user's request onto the real subcommands and flags in the --help blocks below (regenerated from the CLI by scripts/sync_plugins.py; if the installed carrel sign --help differs, trust the installed version — never invent flags):
Usage: carrel sign [OPTIONS] COMMAND [ARGS]...
Sign things: stamp PDFs, hash manifests, verify both.
Options:
--json Machine-readable JSON output.
--help Show this message and exit.
Commands:
manifest Write a sha256 manifest for PATHS (directories recurse).
stamp Stamp a visible signature block onto a PDF page.
verify Recompute a sha256 manifest (and its gpg signature, if present).
Usage: carrel sign manifest [OPTIONS] PATHS...
Write a sha256 manifest for PATHS (directories recurse).
Options:
-o, --out PATH Manifest file to write (sha256sum format). [default: MANIFEST.sha256]
--gpg Also write a detached armored signature (OUT.asc).
--key ID gpg key id/email to sign with (implies --gpg).
--force Allow overwriting an existing manifest.
--json Machine-readable JSON output.
--help Show this message and exit.
Usage: carrel sign stamp [OPTIONS] SRC
Stamp a visible signature block onto a PDF page.
Options:
--text TEXT Stamp text. Default: "Signed by <user> on <ISO date>".
--image PATH Signature image (png/jpg) drawn above the text.
--page PAGE Page to stamp: 'first', 'last' or a 1-based number. [default:
last]
--pos [top-left|top-right|bottom-left|bottom-right]
Page corner for the stamp. [default: bottom-right]
-o, --out PATH Output file. Default: SRC.signed.pdf.
--force Allow overwriting an existing output file.
--json Machine-readable JSON output.
--help Show this message and exit.
Usage: carrel sign verify [OPTIONS] MANIFEST
Recompute a sha256 manifest (and its gpg signature, if present).
Options:
--json Machine-readable JSON output.
--help Show this message and exit.
- stamp SRC: draws a visible signature block (
--text, default "Signed by on "; optional--imagepng/jpg above it) on--page first|last|Nat--pos <corner>. OutputSRC.signed.pdfby default; the original is untouched. This is a visible mark, not a cryptographic PDF signature — say so when the user asks about legal/cryptographic signing, and point them atmanifest --gpgfor integrity. - manifest PATHS...: writes a
sha256sum-format manifest (MANIFEST.sha256by default,-oto choose; directories recurse).--gpg(or--key ID, which implies it) also writes a detached armored signatureOUT.asc— needs gpg with a usable key (exit 3 → relay the hint). - verify MANIFEST: recomputes every hash and, when
MANIFEST.ascexists, checks the gpg signature. Interpret the JSON: list files that areok,changed, ormissing, and the signature result.
Never pass --force unless the user explicitly wants an existing output/manifest replaced. Use --json and report the output path(s); after stamp, confirm with carrel inspect OUT --json that the page count is unchanged. For the redact → verify → manifest flow see this plugin's document-clerk agent.
Requires the carrel CLI on PATH. If carrel is not found, tell the user to install it with uv tool install carrel (see the repo's INSTALL notes), or run it as uv run carrel ... from the carrel repo root.
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.
- yesterday First seen · 78 lines · 34 tokens per session scan A ff42b7b58b8d
sign is a command published in the GitHub repository coltonbearden/carrel (1 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 1,017 once invoked, about $0.0002 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-09-05.
Other commands, from other repositories
receipt
Upload and process receipt images or PDF invoices, extract line items, and match to bank transactions.
sheet-report
Analyze a Numbers or Excel file and generate a report with charts.
cabinet
Build a self-contained archive bundle for a single .eml — markdown, retained attachments, and source file in one directory.
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.