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/co-cart/co-cart/wordpress-reviewgit clone --depth 1 https://github.com/co-cart/co-cartWrote 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/co-cart/co-cart/wordpress-review)<a href="https://agentmods.dev/agents/co-cart/co-cart/wordpress-review"><img src="https://agentmods.dev/badge/agents/co-cart/co-cart/wordpress-review.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.00020 | $0.00584 |
| Opus 5 | $0.00010 | $0.00292 |
| Sonnet 5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
wordpress-review 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 94 lines · 20 tokens per session scan A 636289b741f8
wordpress-review is an agent published in the GitHub repository co-cart/co-cart (411 stars, last pushed yesterday), with no licence file. It adds 20 tokens to every session and 584 once invoked, about $0.0001 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-01.
Other agents, from other repositories
woocommerce-core-dev
Use this agent when you need expert guidance on WooCommerce Core development, including writing or reviewing code that extends, integrates with, or modifies WooCommerce; implementing custom payment gateways, shipping methods, or product types; working with WooCommerce hooks, filters, and APIs; debugging…
issue-tracker
Issues and specs for this repo live as GitHub issues. Use the gh CLI for all operations.
orquestra
Central Orquestra orchestrator. Handles ANY Solana task end-to-end by delegating to four specialized sub-agents in sequence. Always start here — this agent decides which sub-agents to invoke and in what order. Sub-agents it controls: orquestra-researcher — program discovery, docs, instruction listing…
orquestra-pda-explorer
Derives Program Derived Addresses (PDAs) from known seeds and fetches their on-chain data via Orquestra MCP. Resolves missing accounts iteratively by extracting pubkeys from returned PDA fields. Uses ONLY Orquestra MCP tools. Examples: Context: User needs to find a user's stake account for a specific program user…
orquestra-signer
Signs and submits Solana transactions using @orquestradev/signer-mcp. Accepts a base64-encoded wire transaction produced by orquestra-tx-builder, presents a human-readable approval summary, and signs + sends only after explicit user confirmation. Uses ONLY signer-mcp tools. Examples: Context: User has an unsigned…
orquestra-tx-builder
Builds unsigned Solana transactions using Orquestra MCP's buildinstruction tool. Requires all accounts and arguments to be fully resolved before calling. Outputs a base64-encoded wire transaction (Solana RPC standard) ready for signing. Uses ONLY Orquestra MCP tools. Examples: Context: All accounts are known, user…