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 indranilbanerjee/neels-plugins --skill import-sopgit clone --depth 1 https://github.com/indranilbanerjee/neels-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/skills/indranilbanerjee/neels-plugins/import-sop)<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/import-sop"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/import-sop/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/indranilbanerjee/neels-plugins/import-sop"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/import-sop.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.00023 | $0.01453 |
| Opus 5.5 | $0.00009 | $0.00581 |
| Sonnet 5.5 | $0.00005 | $0.00291 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
import-sop 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 2d 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.
This is a copy
89% identical to import-sop — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:import-sop
Purpose
Import and structure agency Standard Operating Procedures (SOPs) that apply across all clients. SOPs define how work gets done — approval workflows, content review steps, campaign launch checklists, escalation procedures, and quality gates.
SOPs are stored at the agency level (~/.claude-marketing/sops/), not per-brand, so they apply consistently across all clients.
Input Required
The user provides:
- SOP content: Pasted workflow steps, checklist items, or process descriptions
- SOP name: What this SOP covers (e.g., "content-approval", "campaign-launch", "crisis-escalation")
- Description (optional): Brief summary of when this SOP applies
If the user doesn't provide a name, infer it from the content.
Process
-
Load brand context: Read
~/.claude-marketing/brands/_active-brand.jsonfor the active slug, then load~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for existing guidelines at~/.claude-marketing/brands/{slug}/guidelines/_manifest.json— if present, load restrictions and relevant category files. Check for custom templates at~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. -
Classify the SOP type:
- Content workflow: Review, approval, and publishing steps for content
- Campaign checklist: Pre-launch, launch, and post-launch verification steps
- Escalation procedure: Who to contact, decision authority, response timelines
- Quality assurance: Testing steps, brand compliance checks, accessibility verification
- Client onboarding: Steps for setting up a new client in the system
- Reporting workflow: Data collection, analysis, presentation, delivery steps
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.
- 2d ago First seen · 141 lines · 23 tokens per session scan A 85ae641d31fd
import-sop is a skill published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 1,453 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to import-sop, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
yearly-planner
Produce the Part 8 yearly planner: quarterly themes and monthly initiatives. "plan the whole year month by month".
import-sop
Import agency procedures as role-assigned SOP steps with approval gates. "import our launch checklist".
webinar-plan
Plan a webinar end to end: run of show, registration copy, promotion, follow-up. "plan a webinar on X".
client-onboarding
Build a client onboarding pack: kickoff agenda, discovery questions, 30-60-90. "we just signed a new client".
marketing-project-mgmt
Marketing project management and execution excellence for B2B SaaS campaigns. Use this skill when coordinating multi-channel campaigns, allocating team resources, planning agile marketing sprints, running QBRs with clients, managing project timelines, balancing marketing workload, or implementing marketing operations…
hoo-task-board
Use to view or mirror the work queue - "task board", "show the queue", /organic-os:task-board. Mirrors to Notion when that connector exists; local queue.md is the source of truth.