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 four-core-documentsgit 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/four-core-documents)<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/four-core-documents"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/four-core-documents/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/four-core-documents"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/four-core-documents.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.00030 | $0.04103 |
| Opus 5.5 | $0.00012 | $0.01641 |
| Sonnet 5.5 | $0.00006 | $0.00821 |
| Haiku 4.5 | $0.00003 | $0.00410 |
Grade A, and why
four-core-documents 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
92% identical to four-core-documents — 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:four-core-documents — The Strategic Spine (61 Steps)
This skill produces Part 3 of the engagement methodology: the four documents that together define the brand at strategic depth. Every channel strategy, every creative brief, every piece of copy reads back to these.
Context efficiency
Heavy skill. Grep before Read any referenced file, then Read only matched ranges with offset + limit. List the brand's workspace at ~/.claude-marketing/brands/{slug}/ (or $CLAUDE_PLUGIN_DATA/digital-marketing-pro/brands/{slug}/ when that env var is set) before opening files. On re-invocation mid-session, skip files already in context.
Specification: four-core-documents-spec.md — the exact 61 steps across the four documents.
Engagement context: engagement-flow-methodology.md — where Part 3 fits in the 12-Part flow.
Pre-conditions
Before running this skill, verify:
- Brand profile exists at
~/.claude-marketing/brands/{brand-slug}/profile.json. If not, run/digital-marketing-pro:brand-setupfirst. - Engagement is initialised with state file
_engagement.jsonpresent. If not, run/digital-marketing-pro:engagement startfirst. - Part 1 (Client Inputs) is completed. Stone facts and Opinion hypotheses must be captured before Part 3 can begin.
- Part 2 (External Research) is at least started. Some Part 2 research may continue in parallel with Part 3, but the kickoff must have happened.
If any pre-condition fails, do NOT produce output. Instead, instruct the user on what to run first.
Subcommands
Produce all four documents
/digital-marketing-pro:four-core-documents <brand-slug> <engagement-id>
Produces 3.1, 3.2, 3.3, 3.4 in sequence. Actual time varies with engagement complexity.
Produce a single document
/digital-marketing-pro:four-core-documents <brand-slug> <engagement-id> --doc 3.1
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 · 360 lines · 30 tokens per session scan A bf58fa051f6a
four-core-documents is a skill published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 4,103 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to four-core-documents, 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".