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 FrkAk/piyaznpx agentmods add plugins/frkak/piyaz/marketplacegit clone --depth 1 https://github.com/FrkAk/piyazWrote 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/frkak/piyaz/marketplace)<a href="https://agentmods.dev/plugins/frkak/piyaz/marketplace"><img src="https://agentmods.dev/badge/plugins/frkak/piyaz/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
piyaz 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 4d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 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.
- 4d ago First seen · 18 lines scan A 5f042ae30f8f
piyaz marketplace is a plugin published in the GitHub repository FrkAk/piyaz (188 stars, last pushed 3d ago), licensed AGPL-3.0. 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-30.
Other plugins, from other repositories
alive
Local, user-owned context for Claude Code. Keep your work in files you control.
ballast
Builds up to a goal in a field you have no expertise in: splits it into the foundations that goal actually needs, mobilizes what you already hold, learns what is missing, and leaves every solved path behind for the next goal. Nothing is called done until a check passes.
orchestrator
Token-frugal multi-agent orchestration for Claude Code, built for a Claude Fable 5 chair: Fable plans and decides, Sonnet 5 carries the volume, Opus 5 takes the hard slices and escalations — each worker's effort sized by the chair — and a two-tier verification valve guards the close. When the Fable limit runs dry, an…
evolving-lite
Self-evolving Claude Code system that learns from corrections, manages context, and improves every session.
consolidate-memory
Cross-project, verification-first memory for Claude Code — the layer beyond the built-in Auto Dream. Shares memory across enrolled projects in the same trust domain (a governed store, replicated into those projects) and verifies facts against the live code (grep/file/git), dropping what it can't confirm — fact-checked.
dream-beta-tester
Beta-tests the consolidate-memory "dream" skill ITSELF — the QA companion to it. A deterministic invariant oracle plus a judgment-lens skill (/dream-beta-test) that finds defects, regressions, and dishonest reports in the dream/consolidation skill, honest by construction (confirmed defects are kept separate from…