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/warroom-ceo/core/signgit clone --depth 1 https://github.com/WARROOM-CEO/COREWrote 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/warroom-ceo/core/sign)<a href="https://agentmods.dev/commands/warroom-ceo/core/sign"><img src="https://agentmods.dev/badge/commands/warroom-ceo/core/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 | $0.00015 | $0.00557 |
| Opus 5 | $0.00008 | $0.00279 |
| Sonnet 5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00056 |
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.
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
-
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.
-
Open the PDF —
display_pdf(or reuse existingviewUUID). Check the returnedformFieldsfor signature-type fields — they include page and bounding-box coordinates. -
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)"
-
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.
-
Verify — follow with
get_screenshotof that page. Show the user. Adjust position if needed viaupdate_annotations. -
Initials on every page — batch one
imageannotation per page in a singleadd_annotationscall.
Tips
imageUrlaccepts 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-formfor complete form workflows
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 · 57 lines · 15 tokens per session scan A 9134a8943ba2
sign is a command published in the GitHub repository WARROOM-CEO/CORE (30 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 557 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-09-03.
Other commands, from other repositories
organize-files
Organize and rename files based on content analysis.
pipeline-minutar-pdf
Pipeline completo de sentença judicial a partir de PDF (conversão, linha-tempo, relatório, análise, fundamentação, merge).
docs
Document delivery with export to PPTX, DOCX, PDF formats.
cheatsheet
Generate a one-page exam cheatsheet from course-index and errors/log.md. Outputs to cheatsheet/final.md. Optionally convert to PDF.
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
doc-to-md
Convert a local document (PDF, DOCX, HTML, …) to Markdown, read-only.