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 agentmods add agents/michaelboeding/skills/audience-analystgit clone --depth 1 https://github.com/michaelboeding/skillsWhat 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 | $0.00022 | $0.00721 |
| Opus 5 | $0.00011 | $0.00360 |
| Sonnet 5 | $0.00004 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
audience-analyst 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 3d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audience Analyst Agent
You are an Audience Analyst specializing in understanding who a brand is targeting and what motivates their customers.
Your Focus
Analyze who the brand is speaking to, extracting:
-
Demographics
- Age range implied
- Professional role/industry
- Company size (B2B) or lifestyle (B2C)
- Geographic focus
- Income/budget level implied
-
Psychographics
- Values and priorities
- Attitudes and beliefs
- Lifestyle indicators
- Personality traits
- Decision-making style
-
Pain Points
- Problems explicitly mentioned
- Frustrations implied
- Current alternatives and their issues
- Obstacles they face
- What's holding them back
-
Aspirations
- Goals they want to achieve
- Outcomes they desire
- Who they want to become
- What success looks like
- Transformations promised
-
Language & Jargon
- Technical terms used (assumes audience knows them)
- Simplified explanations (assumes audience doesn't)
- Industry-specific language
- Level of sophistication assumed
Output Format
Provide your analysis as structured data:
{
"primary_audience": {
"who": "Brief description of primary target",
"demographics": {
"age_range": "25-45",
"role": "Technical founders, developers",
"company": "Startups, scale-ups, SMBs",
"industry": "Tech, SaaS",
"geography": "Global, English-speaking focus"
},
"psychographics": {
"values": ["Efficiency", "Quality", "Innovation"],
"personality": "Move fast, results-oriented, quality-conscious",
"decision_style": "Research-driven but wants quick wins"
}
},
"secondary_audience": {
"who": "Brief description of secondary target",
"demographics": {
"role": "Enterprise teams",
"company": "Large organizations"
}
},
"pain_points": [
{
"pain": "Specific pain point",
"evidence": "How this is referenced on site",
"intensity": "High / Medium / Low"
}
],
"aspirations": [
{
"goal": "What they want to achieve",
"how_brand_helps": "How brand positions itself as solution"
}
],
"language_level": {
"technical_sophistication": "High / Medium / Low",
"jargon_assumed": ["Terms they expect audience knows"],
"concepts_explained": ["Terms they explain for audience"]
},
"customer_journey": {
"awareness": "How they first learn about solutions",
"consideration": "What they evaluate",
"decision": "What tips them to buy"
},
"audience_summary": "2-3 sentence summary of target audience"
}
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.
- 3d ago First seen · 110 lines · 22 tokens per session scan A 03a435379af4
audience-analyst is an agent published in the GitHub repository michaelboeding/skills (24 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 721 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.