goal-filter

goal-filter is a skill for Claude Code from indranilbanerjee/digital-marketing-pro. It costs 24 tokens per session (834 once invoked), scanned A, original, MIT.

A decision filter that compares every marketing idea or draft with one agreed goal, such as a target number of qualified sales meetings. It labels the item as aligned, partly aligned, or off target, then suggests a correction.

In plain words
What is it for?
It is for checking campaigns, content, plans, and ideas against a single metric and deadline before committing time or budget.
Why use it?
It prevents teams from spending time on work that sounds useful but does not support the main measurable outcome. It also records repeated patterns of work drifting away from that goal.

Skill for Claude Code

Written for Claude Code: user-invocable 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 checking campaigns, content, plans, and ideas against a single metric and deadline before committing time or budget.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/indranilbanerjee/digital-marketing-pro/goal-filter
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 goal-filter
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 goal-filter

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/goal-filter"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/goal-filter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 834 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.00024 $0.00834
Opus 5.5 $0.00010 $0.00334
Sonnet 5.5 $0.00005 $0.00167
Haiku 4.5 $0.00002 $0.00083

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

Security

Grade A, and why

goal-filter 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 4d 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/goal-filter/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/digital-marketing-pro:goal-filter

The strategic filter. One goal is locked per brand; everything gets measured against it before time or budget is committed. Marketing fails quietly by doing good work toward nothing in particular — every piece defensible, the quarter's number missed anyway.

State

The locked goal lives in the brand workspace, so every session reads the same one:

~/.claude-marketing/brands/{brand-slug}/goal-lock.json
{
  "goal": "40 qualified demo bookings per month from organic + email",
  "metric": "demo bookings attributed to owned channels",
  "target": 40,
  "deadline": "2026-12-31",
  "locked_at": "2026-08-12",
  "history": [
    {"checked": "2026-08-14", "item": "podcast idea", "verdict": "OFF"}
  ]
}

No file → this is the first run: ask for the goal, force it to one sentence with a metric and a deadline, confirm, write the file. If the user names three goals, make them rank — the filter is useless with more than one.

Judging an item

Read the locked goal, read what the user brought, and rule honestly:

# Goal check — {the locked goal}

## What you brought
[One line]

## Verdict: ON GOAL / PARTIAL / OFF GOAL

## Why (2-3 sentences)
[Does this move the goal's metric? How directly? What is the opportunity cost —
what on-goal work does this displace?]

## The fix (if PARTIAL or OFF)
[The specific change that would make it serve the goal — or "park it", with
what to do instead]

## The sharper version (always)
[The same idea, rewritten to pull harder toward the metric]

Append the verdict to history in the state file.

Critical rules

  • ONE goal at a time. Multiple goals are a priority argument the user has not had yet. Force the ranking before locking anything.
  • Rule honestly. OFF GOAL is a legitimate verdict, and the filter is worthless if it rubber-stamps. An agency that never says "this doesn't serve your objective" is a vendor, not a partner.
  • Never just judge — always hand back an action. The fix or the sharper version, every time. The user leaves with something to do, not just a grade.
  • Name patterns across checks. The history is there to be read: three OFF verdicts in a week is not three isolated ideas, it is a drift — say so, and ask what is pulling attention off the goal. This is the filter's second job: the single verdicts protect the quarter, the pattern protects the strategy.
  • Goals are marketing outcomes — revenue, qualified leads, audience quality, authority in a niche, retention. "More followers" is accepted only with a because-clause that survives one round of "and what does that get you?".
  • Changing the goal is allowed, silently drifting is not. --set on an existing lock archives the old goal into history with its end date, so the quarter's record shows one deliberate change rather than a smear.
  • Engagement integration: inside a 12-Part engagement, the engagement's objectives are the goal source — offer to lock Part 1's primary objective rather than inventing a parallel one.

Read the full file on GitHub · 90 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. 4d ago Changed · -123 tokens per session 7b3886a095bd
  2. 1mo ago First seen · 90 lines · 147 tokens per session scan A 66bc7355cef2

Subscribe to this mod's changes

goal-filter is a skill published in the GitHub repository indranilbanerjee/digital-marketing-pro (882 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 834 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.