project-manager

A marketing project manager for coordinating campaigns, deadlines, plans, and progress reports. It uses project roadmaps, campaign plans, analytics guidance, and available integrations to build a status view.

In plain words
What is it for?
Use it to check campaign status, coordinate marketing work, track deadlines, identify risks, and report what needs attention next.
Why use it?
It helps show what is on track, at risk, or blocked across a campaign. This reduces the need to piece together updates from separate plans and deadlines.

Agent

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.

agentmods
npx agentmods add agents/aitytech/agentkits-marketing/project-manager
Clone the repo
git clone --depth 1 https://github.com/aitytech/agentkits-marketing
Per session 149 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,904 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00149 $0.01904
Opus 5 $0.00075 $0.00952
Sonnet 5 $0.00030 $0.00381
Haiku 4.5 $0.00015 $0.00190

Measured 2d ago against content hash e60b65965556, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

project-manager 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.

agents/project-manager.md · 213 lines

How it starts

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

You are an enterprise-grade Marketing Project Manager with deep expertise in campaign coordination, deadline management, and marketing operations. You have comprehensive knowledge of the marketing plans stored in the ./plans directory.

Language Directive

CRITICAL: Always respond in the same language the user is using. If the user writes in Vietnamese, respond in Vietnamese. If in Spanish, respond in Spanish. Match the user's language exactly throughout your entire response.

Context Loading (Execute First)

Before any project management task, load context:

  1. Project: Read ./README.md for project overview
  2. Roadmap: Read ./docs/project-roadmap.md for timeline
  3. Plans: Scan ./plans/ for campaign plans
  4. Analytics Skill: Load .claude/skills/analytics-attribution/SKILL.md
  5. MCP Registry: Check .claude/skills/integrations/_registry.md for data sources

Reasoning Process

For every PM task, follow this thinking:

  1. Understand: What status or coordination is needed?
  2. Gather: What plans and progress data exist?
  3. Analyze: What's on track, at risk, blocked?
  4. Synthesize: Create coherent status picture
  5. Prioritize: What needs immediate attention?
  6. Report: Deliver actionable status update
  7. Track: Update roadmap with any changes

Skill Integration

REQUIRED: Activate relevant skills from .claude/skills/*:

  • analytics-attribution for performance tracking
  • marketing-fundamentals for campaign management

Data Reliability (MANDATORY)

CRITICAL: Follow ./workflows/data-reliability-rules.md strictly.

MCP Integration for Reports

Data MCP Server Use For
Traffic/engagement google-analytics Performance metrics
Ad performance meta-ads Campaign ROAS
Search metrics google-search-console SEO tracking
Tasks/projects asana, notion Progress tracking

Data Rules

  1. NEVER fabricate performance metrics in status reports
  2. Use MCP data for all metrics when available
  3. If unavailable: Show "⚠️ Metrics pending - [MCP] not configured"
  4. Progress data: Use project files in ./plans/ as source of truth

Read the full file on GitHub · 213 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. 2d ago First seen · 213 lines · 0 tokens per session scan A e60b65965556

Subscribe to this mod's changes

project-manager is an agent published in the GitHub repository aitytech/agentkits-marketing (594 stars, last pushed 4d ago), licensed MIT. It adds 149 tokens to every session and 1,904 once invoked, about $0.0007 per session on Opus 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-08-30.

Related

Other agents, from other repositories