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-guidelinesgit 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-guidelines)<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/import-guidelines"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/import-guidelines/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-guidelines"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/import-guidelines.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.00027 | $0.01471 |
| Opus 5.5 | $0.00011 | $0.00588 |
| Sonnet 5.5 | $0.00005 | $0.00294 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
import-guidelines 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
91% identical to import-guidelines — 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:import-guidelines
Purpose
Import and structure brand guidelines into the persistent brand knowledge layer. Converts unstructured guideline documents, style guides, restriction lists, and messaging playbooks into structured, enforceable markdown files that are automatically applied across all modules and commands.
Input Required
The user provides one or more of:
- Pasted guideline content: Text from an existing brand guide, style guide, or restriction list
- Verbal description: Spoken/typed rules ("we never use exclamation marks", "always lead with data")
- Category to update: Which guideline category to add to (voice-and-tone, messaging, restrictions, channel-styles, visual-identity, or custom)
- Source document reference: Description of where these guidelines come from
If the user doesn't specify a category, analyze the content and route it to the correct category automatically.
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 existing guidelines to merge with (not overwrite). If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. -
Classify the content — Determine which guideline category (or categories) the input belongs to:
- Voice rules, writing style, tone →
voice-and-tone.md - Key messages, taglines, positioning, value props →
messaging.md - Banned words, restricted claims, disclaimers, prohibited topics →
restrictions.md - Per-channel format/tone rules →
channel-styles.md - Colors, fonts, logo rules, imagery style →
visual-identity.md - Anything else →
custom/{descriptive-name}.md
- Voice rules, writing style, tone →
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 · 125 lines · 27 tokens per session scan A 49139b2cb214
import-guidelines is a skill published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 1,471 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to import-guidelines, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
continuous-improvement-loop
Run the Part 12 continuous improvement loop into a quarterly brief for leadership. "produce the quarterly improvement brief".
yearly-planner
Produce the Part 8 yearly planner: quarterly themes and monthly initiatives. "plan the whole year month by month".
attribution-report
Run attribution on real conversion paths, comparing models. "which channels actually drive revenue".
validate-output
Validate content structure against a schema: sections, word counts. "scan for leftover placeholders".
add-integration
Add a custom MCP integration: scaffold the server, write .mcp.json, test it. "add a new MCP server".
client-proposal
Draft a client proposal or RFP response: scope, deliverables, KPIs, pricing tiers. "respond to this RFP".