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/bjorn-ingmanson/thefroject-plugins/sowgit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-pluginsWrote 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/bjorn-ingmanson/thefroject-plugins/sow)<a href="https://agentmods.dev/commands/bjorn-ingmanson/thefroject-plugins/sow"><img src="https://agentmods.dev/badge/commands/bjorn-ingmanson/thefroject-plugins/sow.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.00000 | $0.00345 |
| Opus 5 | $0.00000 | $0.00172 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
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 5d 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.
What it actually says
/sow — Generate Statement of Work
Generate a ready-to-sign statement of work from proposal context.
Before you start
Read these skill files if they exist:
.claude/skills/proposal-voice/— copywriting rules for all client-facing docs.claude/skills/pricing-guidelines/— tiers, engagement models, pricing copy rules
Workflow
- Gather inputs:
- Read any existing proposal or demo deck in
outputs/ - Client name, project name, and engagement type
- Scope agreed during sales process
- Timeline and milestones
- Pricing and payment terms (reference pricing-guidelines)
- Read any existing proposal or demo deck in
- Generate the SOW:
- Parties — Your company and the client, with contacts
- Background — Brief context on why this engagement exists
- Scope of work — Specific deliverables with acceptance criteria
- Out of scope — Explicit boundaries to prevent scope creep
- Timeline — Milestones with dates and dependencies
- Team — Who's involved and their roles
- Investment — Pricing breakdown, payment schedule, terms
- Assumptions — What needs to be true for this to work
- Change process — How scope changes are handled
- Save to
outputs/sow-[client-name].md
Usage: /sow [client name] [optional: engagement type or reference to proposal]
Examples:
/sow Acme Corp — based on the demo-proposal in outputs//sow Northwind Traders — 3-month advisory engagement
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.
- 5d ago First seen · 33 lines · 0 tokens per session scan A 4d7246b8e08d
sow is a command published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 345 tokens. 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 commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
review-policy
Review a policy document for structure, coverage, and language quality.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.