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 skills add rossumai/claude-marketplace --skill write-sowgit clone --depth 1 https://github.com/rossumai/claude-marketplaceWrote 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/rossumai/claude-marketplace/write-sow)<a href="https://agentmods.dev/skills/rossumai/claude-marketplace/write-sow"><img src="https://agentmods.dev/badge/skills/rossumai/claude-marketplace/write-sow/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/rossumai/claude-marketplace/write-sow"><img src="https://agentmods.dev/badge/skills/rossumai/claude-marketplace/write-sow.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.00074 | $0.02685 |
| Opus 5 | $0.00037 | $0.01342 |
| Sonnet 5 | $0.00015 | $0.00537 |
| Haiku 4.5 | $0.00007 | $0.00268 |
Grade A, and why
write-sow 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 11d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Rossum.ai Solution Architect writing a Statement of Work. Generate a SOW based on the following project requirements:
$ARGUMENTS
Instructions
-
Gather requirements. If the user has not provided enough context (or no arguments were given), ask clarifying questions. Focus on:
- Document types: What documents will be processed? (invoices, purchase orders, delivery notes, receipts, etc.)
- Queues: How many queues are needed? Are they split by country, document type, or business unit?
- Fields: What header fields and line items need to be extracted?
- Integrations: What downstream systems will receive the data? (SAP, Coupa, NetSuite, Workday, custom ERP, SFTP/S3)
- Master data: Does the customer need vendor matching, PO matching, or other data validation? What fields should be used for matching (VAT ID, IBAN, name, PO number)? What datasets will be provided and in what format?
- Out of scope: What is explicitly excluded?
If the customer's Data Storage environment is accessible (via the
rossum-apiMCP tools), usedata_storage_list_collectionsto discover existing datasets anddata_storage_aggregateto sample their structure (e.g.[{"$sample": {"size": 1}}]). This reveals what master data is already available, what fields exist, and what matching strategies are feasible — use these findings to inform the Master Data Hub deliverables rather than guessing. -
Generate the SOW using the exact structure from template.md. Every generated SOW must follow this template — do not add, remove, or reorder sections.
-
Verify deliverability. Before writing the final SOW, cross-check every deliverable against the Rossum platform reference (auto-loaded via the
rossum-referenceskill) and MongoDB reference (auto-loaded via themongodb-referenceskill). Confirm that each promised feature, integration, or configuration is actually supported by the platform. If a deliverable cannot be verified against the reference, flag it to the user before including it. If Data Storage is accessible, verify that referenced collections actually exist and that their field names match what the SOW promises. -
Write the SOW as a new markdown file named
SOW-[project-name].mdin the current working directory.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 122 lines · 74 tokens per session scan A 16be76fb3ed8
write-sow is a skill published in the GitHub repository rossumai/claude-marketplace (5 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 2,685 once invoked, about $0.0004 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 skills, from other repositories
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
overleaf-sync
A two-way connection between a local paper folder and Overleaf, a web-based LaTeX editor for writing research papers. It lets you move changes between the local files and the shared Overleaf project.