four-core-documents

four-core-documents is a skill for Claude Code from indranilbanerjee/digital-marketing-pro. It costs 30 tokens per session (4,103 once invoked), scanned A, original, MIT.

A set of four strategy documents covering business analysis, customer segments, brand positioning, and the way digital marketing activities fit together. It can produce the documents separately or combine them into one executive version.

In plain words
What is it for?
It is for defining a brand's business context, target groups, market position, communications direction, and overall digital-marketing framework.
Why use it?
It gives later marketing work a shared strategic reference instead of making each campaign start from different assumptions. The documents require an existing brand profile and engagement setup.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Part of the digital-marketing-pro plugin — 164 skills, 5 commands, 24 agents shipped together

Good fit It is for defining a brand's business context, target groups, market position, communications direction, and overall digital-marketing framework.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/indranilbanerjee/digital-marketing-pro/four-core-documents
Install

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.

Any agent
npx skills add indranilbanerjee/digital-marketing-pro --skill four-core-documents
Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro

Made for: Claude Code.

Or install digital-marketing-pro, the plugin that ships this one along with the rest of its 164 skills, 5 commands, 24 agents.

Wrote 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.

agentmods badge for four-core-documents

README.md
[![agentmods](https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/four-core-documents/github.svg)](https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/four-core-documents)
Your own site
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/four-core-documents"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/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.

agentmods 80×15 button for four-core-documents

Your own site · 80×15
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/four-core-documents"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/four-core-documents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,103 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 17d ago against content hash bf58fa051f6a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 17d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/four-core-documents/SKILL.md · 360 lines

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:

  1. Brand profile exists at ~/.claude-marketing/brands/{brand-slug}/profile.json. If not, run /digital-marketing-pro:brand-setup first.
  2. Engagement is initialised with state file _engagement.json present. If not, run /digital-marketing-pro:engagement start first.
  3. Part 1 (Client Inputs) is completed. Stone facts and Opinion hypotheses must be captured before Part 3 can begin.
  4. 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

Read the full file on GitHub · 360 lines

Changes

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.

  1. 17d ago Changed · -134 tokens per session bf58fa051f6a
  2. 22d ago Changed · -9 lines e8439dbb334c
  3. 1mo ago First seen · 369 lines · 164 tokens per session scan A 39a9c7827170

Subscribe to this mod's changes

four-core-documents is a skill published in the GitHub repository indranilbanerjee/digital-marketing-pro (911 stars, last pushed today), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.