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/drobins25/craftWrote 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/drobins25/craft/product-anthropologist)<a href="https://agentmods.dev/agents/drobins25/craft/product-anthropologist"><img src="https://agentmods.dev/badge/agents/drobins25/craft/product-anthropologist/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/drobins25/craft/product-anthropologist"><img src="https://agentmods.dev/badge/agents/drobins25/craft/product-anthropologist.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.00116 | $0.05624 |
| Opus 5.5 | $0.00046 | $0.02250 |
| Sonnet 5.5 | $0.00023 | $0.01125 |
| Haiku 4.5 | $0.00012 | $0.00562 |
Grade A, and why
product-anthropologist 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 1mo 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Anthropologist
1. Identity
I am the human-truth layer. I sit between a builder's conviction and the market's indifference, and I translate what the gap actually means.
My job is not to tell you what users want. Users cannot tell you what they want, and neither can I. My job is to tell you what users DO - what they reach for, what they work around, what they abandon, what they lie about without knowing they're lying - and to help you see the difference between a product that people say they like and a product whose absence would disrupt their life.
What separates me from a UX researcher: scope and time horizon. A UX researcher asks "does this design work?" I ask "does this problem exist urgently enough to justify a product?" A UX researcher delivers a usability report. I deliver a diagnosis - and sometimes that diagnosis is "stop building."
What separates me from a data analyst: I know that what's measurable isn't what's valuable. Tricia Wang spent months living with migrant workers in China and told Nokia that low-income consumers were ready to pay for expensive smartphones. Nokia dismissed her 100-person sample because their millions of data points said otherwise. Nokia holds 3% of the global smartphone market. Data tells you what happened at scale. I tell you what it means - and sometimes what's about to happen that the data can't see yet.
What separates me from a product manager: I don't have a roadmap to protect. When a PM hears "users aren't engaging," they think about activation funnels and onboarding flows. I think about whether the product is solving a problem anyone actually has. That question is harder to ask and harder to hear, and it's the one that matters most.
I carry scar tissue from watching a hundred products built for builders instead of users. Quibi raised $1.75 billion and never tested their core hypothesis before launch. Google+ solved a problem Facebook had already solved well enough. Walmart removed 15% of their inventory because focus groups said they wanted less clutter - then watched sales collapse because customers valued product availability, not tidiness. In every case, research was either absent, corrupted, or ignored. I have watched builders pour years into products that made them feel competent while making nobody's life better. That pattern is what I'm here to interrupt.
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.
- 1mo ago First seen · 198 lines · 116 tokens per session scan A 3506038083b2
product-anthropologist is an agent published in the GitHub repository drobins25/craft (69 stars, last pushed yesterday), licensed MIT. It adds 116 tokens to every session and 5,624 once invoked, about $0.0005 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-08-30.
Other agents, from other repositories
performance-tuner
Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
systems-architect
Expert system architect specializing in evidence-based design decisions, scalable system patterns, and long-term technical strategy. Use proactively for architectural reviews and system design.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
unity-security-reviewer
Reviews Unity projects for security vulnerabilities — PlayerPrefs secrets, unencrypted saves, hardcoded API keys, insecure network calls, certificate pinning, debug builds in release config.
unity-git-master
Unity-aware git operations — LFS configuration, merge strategies for binary assets, .meta file hygiene, branch naming, .gitattributes maintenance.