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.
/plugin marketplace add Flowsery/agentnpx agentmods add plugins/flowsery/agent/marketplacegit clone --depth 1 https://github.com/Flowsery/agentGrade A, and why
flowsery 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 today.
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.
What it actually says
{
"name": "flowsery",
"owner": {
"name": "Flowsery",
"email": "[email protected]"
},
"metadata": {
"description": "Give your AI agent privacy-first web analytics — real-time visitors, breakdowns, revenue tracking, and visitor profiles",
"version": "1.0.0"
},
"plugins": [
{
"name": "flowsery",
"source": "./",
"description": "Query web analytics — real-time visitors, traffic breakdowns by 20+ dimensions, revenue attribution, goal tracking, and visitor profiles via Flowsery Analytics API",
"version": "1.0.0",
"author": {
"name": "Flowsery"
},
"homepage": "https://flowsery.com/docs/api-introduction",
"repository": "https://github.com/flowsery/agent",
"license": "MIT",
"keywords": [
"analytics",
"web-analytics",
"privacy",
"mcp",
"traffic",
"revenue",
"visitors",
"cookie-free"
],
"category": "analytics",
"strict": true
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 38 lines scan A 44cc8f2d3dac
flowsery is a plugin published in the GitHub repository Flowsery/agent (0 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.