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 scharissis/polakonpx agentmods add plugins/scharissis/polako/marketplacegit clone --depth 1 https://github.com/scharissis/polakoWrote 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/plugins/scharissis/polako/marketplace)<a href="https://agentmods.dev/plugins/scharissis/polako/marketplace"><img src="https://agentmods.dev/badge/plugins/scharissis/polako/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
scharissis marketplace 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": "scharissis",
"owner": {
"name": "Stefano Charissis"
},
"metadata": {
"description": "Personal Claude Code plugins"
},
"plugins": [
{
"name": "polako",
"description": "Works a GitHub issue backlog to zero, unattended: plan proposes it, health audits for it, work drives it to a merged PR.",
"category": "workflow",
"source": {
"source": "github",
"repo": "scharissis/polako",
"ref": "polako--v0.20.0"
}
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
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 Changed b8dacd6fe19c
- 3d ago First seen · 22 lines scan A d540a9be76d8
scharissis marketplace is a plugin published in the GitHub repository scharissis/polako (1 stars, last pushed today), 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
product2prod
AI product-management operating plugin: wizard front door, four evidence-gated verbs, multi-company packs, GTM domain library, consent-gated local telemetry.
shipyard
Turn your idea into working code — Shipyard runs Claude Code through a spec-driven agile sprint lifecycle: discuss features, plan sprints, build with TDD, review, and ship.
backlog
Project backlog manager — records deferred tasks into docs/backlogs/ only when the user asks, when Claude gets consent to defer an unrelated bug or out-of-scope side task, or in a background session needing the user's decision. Never captures silently. Commands to list and manage. Files-based, in-repo, no execution…
ratchet
Verified, resumable engineering loops for Claude Code — audit a codebase into an acceptance-gated backlog, route each item to the right model, execute one verified commit at a time.
engenharia-de-requisitos
Loads canonical knowledge of Requirements Engineering, Business Analysis, and Professional Ethics into any Claude session. Built from the IFPB ERS course material (Prof. Dr. Juliana Dantas Ribeiro Viana de Medeiros) plus the canonical bibliography (Sommerville, Pressman, Wiegers, Cohn, Robertson, Hull, Falbo, BABOK v3.
cc-backlog-connect
Sync Backlog issues to local docs for Claude Code context.