op3-mcp-cli
AGENTS.md0 starsChanged 38 days agoMITView on GitHub
For agents editing this repository. Users read the README. Driving the server is SKILL.md. 22 read-only tools over OP3, the Open Podcast Prefix Project. OP3 sits in front of the audio file, so it counts every download regardless of which app made it, which is why its numbers differ from Apple's or Spotify's own dashboards. Commit as n@navid.me. Never pass -c user.email=. The global config is correct and the override is the bug. Everything reads. There is no write path,…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- op3-podcast-analyticsSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Commit as
n@navid.me: Never pass -c user.email=.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Working on op3-mcp
For agents editing this repository. Users read the README. Driving the server is
SKILL.md.
What this is
22 read-only tools over OP3, the Open Podcast Prefix Project. OP3 sits in front of the audio file, so it counts every download regardless of which app made it, which is why its numbers differ from Apple's or Spotify's own dashboards.
Non-negotiables
Commit as n@navid.me. Never pass -c user.email=. The global config is
correct and the override is the bug.
Everything reads. There is no write path, and OP3 exposes none. Do not add a tool that implies otherwise.
No data is the normal answer, not a failure. OP3 only sees a show if the prefix is on its feed, so a feed without it returns nothing and always will. Say that plainly rather than retrying with different arguments, or the model reports a working system as broken.
Never present OP3 numbers as comparable to a platform dashboard. Apple and Spotify report their own listeners only. Explaining the difference is part of answering the question, not a footnote.
The shared preview token is rate limited and is a fallback, not the intended setup. A user hitting limits needs their own token, not a retry.
Before claiming it works
npm run build && npm test && npm run typecheck
npx @modelcontextprotocol/inspector node dist/index.jsDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.