sign

sign is a command for Claude Code from WARROOM-CEO/CORE. It costs 15 tokens per session (557 once invoked), scanned A, original, MIT.

A command for placing an image of a signature or initials onto a PDF page. It does not create a legally certified digital signature.

In plain words
What is it for?
Use it to add a signature image or initials to a selected PDF page and position it in a signature field or specified location.
Why use it?
It provides a visible mark on the document without pretending to replace a dedicated electronic-signing service.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is If you need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md)..

Part of the pdf-viewer plugin — 1 skill, 8 commands shipped together

Good fit Use it to add a signature image or initials to a selected PDF page and position it in a signature field or specified location.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/WARROOM-CEO/CORE
agentmods
npx agentmods add commands/warroom-ceo/core/sign

Made for: Claude Code.

Or install pdf-viewer, the plugin that ships this one along with the rest of its 1 skill, 8 commands.

Wrote 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.

agentmods badge for sign

README.md
[![agentmods](https://agentmods.dev/badge/commands/warroom-ceo/core/sign/github.svg)](https://agentmods.dev/commands/warroom-ceo/core/sign)
Your own site
<a href="https://agentmods.dev/commands/warroom-ceo/core/sign"><img src="https://agentmods.dev/badge/commands/warroom-ceo/core/sign/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.

agentmods 80×15 button for sign

Your own site · 80×15
<a href="https://agentmods.dev/commands/warroom-ceo/core/sign"><img src="https://agentmods.dev/badge/commands/warroom-ceo/core/sign.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 557 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00557
Opus 5.5 $0.00006 $0.00223
Sonnet 5.5 $0.00003 $0.00111
Haiku 4.5 $0.00002 $0.00056

Measured 1mo ago against content hash 9134a8943ba2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

plugins/pdf-viewer/commands/sign.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Language: All user-facing output — responses, summaries, and any text the user will read — must be written in Thai (ภาษาไทย). Internal logic, file paths, code snippets, and technical values remain in English.

If you need to check which tools are connected, see CONNECTORS.md.

Sign PDF

Add a visual signature or initials to a document using an image annotation.

Disclaimer: This places your signature image on the page. It is not a certified or cryptographic digital signature. For legally binding e-signatures, use a dedicated signing service.

Workflow

  1. Get the signature image — ask the user for a local file path (PNG/JPG) to their signature or initials. If they don't have one, suggest they create one and save it to a known path.

  2. Open the PDF — display_pdf (or reuse existing viewUUID). Check the returned formFields for signature-type fields — they include page and bounding-box coordinates.

  3. Locate the target — if there's a signature field, use its coordinates. Otherwise ask: "Which page, and where on the page? (e.g., bottom-right of page 3)"

  4. Place it — interact → add_annotations:

    {"action": "add_annotations", "annotations": [
      {"id": "sig1", "type": "image", "page": 3,
       "imageUrl": "/path/to/signature.png",
       "x": 400, "y": 700, "width": 150}
    ]}
    

    Width/height auto-detected from the image if omitted.

  5. Verify — follow with get_screenshot of that page. Show the user. Adjust position if needed via update_annotations.

  6. Initials on every page — batch one image annotation per page in a single add_annotations call.

Tips

  • imageUrl accepts local file paths or HTTPS URLs (no data: URIs)
  • Users can also drag & drop the signature image directly onto the viewer
  • Coordinate origin is top-left; a typical bottom-right signature on US Letter is around x: 400, y: 700
  • Pair with /pdf-viewer:fill-form for complete form workflows

Read the full file on GitHub · 57 lines

Changes

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.

  1. 1mo ago First seen · 57 lines · 15 tokens per session scan A 9134a8943ba2

Subscribe to this mod's changes

sign is a command published in the GitHub repository WARROOM-CEO/CORE (30 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 557 once invoked, about $0.0001 per session on Opus 5.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-03.