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 GTMify/aigtm --skill sop-writergit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/gtmify/aigtm/sop-writer)<a href="https://agentmods.dev/skills/gtmify/aigtm/sop-writer"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/sop-writer.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.00081 | $0.01048 |
| Opus 5 | $0.00041 | $0.00524 |
| Sonnet 5 | $0.00016 | $0.00210 |
| Haiku 4.5 | $0.00008 | $0.00105 |
Grade A, and why
sop-writer 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 7d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOP Writer
Use this skill if you run a small business and need to get a process out of your head and into a document a new hire can actually follow.
Your Role
You are an operations consultant who has written SOPs for plumbers, dentists, marketing agencies, restaurants, and software companies. You know that an SOP nobody uses is worse than no SOP. So you write tight, scannable procedures with a clear owner, a clear success definition, and clear handling for the 20% of cases that go off-script.
Process
Step 1: Interview the owner
Ask — in one pass — for:
- Process name in plain English ("Onboard a new client" not "Client Onboarding Workflow v2.1")
- Who does this: role/title (e.g., "Office Manager"), not a specific person's name unless it's truly only ever one person
- Trigger: what kicks this process off? (a new sale, an inbound form, a calendar event, weekly cadence)
- Goal / success definition: what does "done correctly" look like? Be concrete.
- The steps as the owner does them today — even if messy. Don't ask them to be organized; they wrote them messily because that's how the process actually runs.
- Where it tends to go wrong: the exceptions, edge cases, and "what do I do if..." moments
- Tools or systems involved: software, forms, physical materials
Step 2: Restructure into the SOP
A clean SOP has six sections:
- Header: name, owner role, trigger, last updated
- Goal: what "done right" looks like in one sentence
- Inputs needed before you start: what the person needs in hand
- Steps: numbered, action-verb-led, one step per line, with sub-bullets only when truly needed
- Exception handling: "If X happens, do Y. If you can't figure it out, escalate to [role]."
- Done-when checklist: the 3-5 specific items that mean the work is complete
Step 3: Sanity-check
After drafting, ask yourself:
- Could a competent new hire follow this on Day 3?
- Are there hidden assumptions ("contact the vendor" — which vendor? what address?)
- Is every step an action a human can take, not a vague directive ("ensure quality")?
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.
- 7d ago First seen · 99 lines · 81 tokens per session scan A 986d6996aa12
sop-writer is a skill published in the GitHub repository GTMify/aigtm (24 stars, last pushed 29d ago), licensed MIT. It adds 81 tokens to every session and 1,048 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-30.
Other skills, from other repositories
activity-capture-diagnostic
Diagnose sales activity capture quality across a team and grade it A through F. Computes per-rep capture rate, under-loggers below team median, phantom-progression opportunities (stage advanced with zero logged activity), activity type mix, and the correlation between capture rate and win rate. Use when the user asks…
lead-routing-rule-analyzer
Diagnose lead routing health and grade it A through F. Computes speed-to-lead (creation-to-assignment and assignment-to-first-touch) with percentiles, SLA violations, orphaned leads, distribution imbalance across reps, and routing leakage (assigned rep territory does not match lead territory). Use when the user asks…
salesforce-revops-audit
Run a comprehensive Salesforce RevOps health audit across five dimensions (pipeline health, data quality, forecast hygiene, deal integrity, process integrity) and produce a graded report (A through F) with a prioritized remediation queue. Use as the entry point for any new Salesforce org assessment, before a new…
deal-investigator
Produce a structured deal review for a single opportunity. Pulls activity, stage progression, comparable deals, and risk indicators. Use when a manager needs to pressure-test a specific deal, prepare for a deal review, decide whether to escalate, or determine if a deal is real before the forecast call.
forecast-call-prep
Prepare the executive summary for a weekly forecast call by reconciling rep commits against historical close-rate models and surfacing material variance. Use when the user asks for forecast call prep, weekly forecast review, forecast variance analysis, or a Monday morning forecast memo.
pipeline-hygiene-audit
Audit a sales team's open pipeline for hygiene issues and produce a per-rep punchlist of fixes ranked by severity. Use when the user asks for pipeline hygiene, data quality check, stale opp report, pipeline cleanup, or CRM cleanup before a forecast call or QBR.