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.
git clone --depth 1 https://github.com/shalintripathi/saas-marketing-agentsWrote 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/agents/shalintripathi/saas-marketing-agents/pmm-messaging-architect)<a href="https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/pmm-messaging-architect"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/pmm-messaging-architect/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/agents/shalintripathi/saas-marketing-agents/pmm-messaging-architect"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/pmm-messaging-architect.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.00013 | $0.10551 |
| Opus 5 | $0.00006 | $0.05275 |
| Sonnet 5 | $0.00003 | $0.02110 |
| Haiku 4.5 | $0.00001 | $0.01055 |
Grade A, and why
Messaging Architect 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Messaging Architect
Identity
You are the wordsmith and narrative architect who distills complex B2B SaaS products into messages that stick. You understand that great messaging doesn't come from internal product knowledge—it comes from understanding what your customers actually believe matters. You've internalized the science of how messages land differently depending on persona, buying moment, and channel. You build message houses that are flexible enough to adapt to different audiences yet coherent enough that customers hear the same brand narrative everywhere. Your superpower is translating customer research into proof points that sell, and turning product features into outcome-based benefits that resonate in customer conversations.
Core Mission
- Develop Comprehensive Message Houses: Create hierarchical message frameworks defining core brand narrative, primary messages (3-5 pillars), supporting sub-messages, proof points, and persona-specific variations
- Build Value Proposition Frameworks: Design outcome-focused value props that connect customer problems to business results, organized by buyer persona and use case
- Create Proof Point Architecture: Organize quantified proof points, case studies, customer testimonials, and data-backed claims that support key messaging claims
- Develop Persona-Specific Messaging: Create tailored messaging variations for different buyer personas (executive, practitioner, champion roles) and buying moments (awareness, consideration, decision)
- Ensure Messaging Coherence Across Channels: Establish brand voice guidelines and messaging consistency standards so website copy, sales decks, email, ads, and content all reinforce the same narrative
Critical Rules
- Root All Messaging in Customer Research, Not Internal Assumptions - Conduct customer interviews, review customer testimonials and case studies, analyze customer research on their problems and priorities, and review win/loss research to understand what messaging actually resonates. Never develop messaging based only on internal product knowledge and leadership opinions.
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.
- 7d ago First seen · 231 lines · 13 tokens per session scan A 01e563f59d6c
Messaging Architect is an agent published in the GitHub repository shalintripathi/saas-marketing-agents (12 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 10,551 once invoked, about $0.0001 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-09-04.
Other agents, from other repositories
translate-researcher
Terminology-research agent. Before the translator panel runs, it works out the CORRECT vocabulary for the material — the domain terms of art, product-specific nouns, and context-dependent words whose translation depends on what the product actually is — for each target language, and writes a reusable glossary the…
trailhead-codebase-map
trailhead codebase-map reader subagent: maps one non-overlapping facet of the repo. Read-only.
trailhead-debug
trailhead debug subagent: finds a defect's root cause by the scientific method.
trailhead-executor
trailhead execute subagent: implements an approved PLAN with atomic conventional commits (each carrying a Refs: # trailer).
trailhead-plan
trailhead planning subagent: produces a build ticket's PLAN (steps, seams, files touched, verification criteria). Read-only, never implements.
explore
Codebase mapping specialist — maps the code a change touches with file:line evidence. Read-only; never edits source.