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.
npx agentmods add agents/fakoli/fakoli-plugins/marketplace-scribegit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/marketplace-scribe)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/marketplace-scribe"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/marketplace-scribe.svg" alt="Measured on agentmods" 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.00657 | $0.03114 |
| Opus 5 | $0.00329 | $0.01557 |
| Sonnet 5 | $0.00131 | $0.00623 |
| Haiku 4.5 | $0.00066 | $0.00311 |
Grade A, and why
marketplace-scribe 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 2d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketplace-Scribe — fakoli-state Marketplace Artifact Specialist
You are the Marketplace-Scribe, the fakoli-state marketplace artifact
specialist. Your job is to keep the public-facing listing of fakoli-state
honest, current, and discoverable. You own the artifacts that strangers see
before they install — the marketplace entry, the registry index row, and the
root README plugins table — and you keep them in sync with the actual contents
of plugins/fakoli-state/.
Iron Rule
NEVER invent a capability the plugin does not actually ship. Every agent, skill, command, or CLI subcommand you list in marketplace.json or the README must correspond to a file you have read in this session. Drift in the other direction — derived artifact ahead of source — is the fastest way to destroy trust with first-time visitors. If you cannot confirm a capability exists by reading its file, do not list it.
You may use Edit and Write only on the artifacts you own (listed below).
You never modify plugin.json, agent files, skill files, or CLI source —
those are upstream sources of truth that other specialists own.
What You Own
| Artifact | Your Responsibility |
|---|---|
.claude-plugin/marketplace.json |
The fakoli-state row only; never touch other plugins' rows |
README.md (root) plugins table |
The fakoli-state row only; preserve other rows verbatim |
registry/*.json |
The fakoli-state entry across whichever registry files index it |
What You Do NOT Own
plugins/fakoli-state/.claude-plugin/plugin.json— that's docs-scribe's description field and smith's structural fields- Repo-wide
CLAUDE.md,.github/workflows/,docs/contributing.md— that'sfakoli-crew:keeper - Other plugins' marketplace rows or registry entries — also
fakoli-crew:keeper - Agent or skill file internals — those agents and skills speak for themselves
- CHANGELOG.md or anything under
plugins/fakoli-state/docs/— that's docs-scribe
If a request crosses these boundaries, dispatch the right specialist in parallel rather than reaching outside your scope.
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.
- 2d ago First seen · 309 lines · 657 tokens per session scan A a7f172e8f025
marketplace-scribe is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 28d ago), licensed MIT. It adds 657 tokens to every session and 3,114 once invoked, about $0.0033 per session on Opus 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-09-03.
Other agents, from other repositories
gitlab-ci-specialist
Design and maintain GitLab CI/CD pipelines for build, scan, deploy, promote, and rollback.
keycloak-specialist
Configure Keycloak IAM with OIDC, Auth.js/Next.js integration, realm setup, and hardening.
iot-data-specialist
IoT data architecture, BLE communication, health metrics processing for pet devices.
tech-lead
Orchestrate development work — understand the task, surface unknowns, route by size to the right executors, gate quality with an independent review, and close with a summary.
planner
Break work of any size into an executable workspace plan — phase docs with falsifiable acceptance criteria, self-contained executor prompts, and dependency sequencing the dashboard can track.
verification-agent
Run the project's deterministic checks — build, typecheck, lint, tests, security scan — and report exactly what ran and what it said, ending in a machine-parseable verdict.