Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add aiocean/claude-plugins/plugin install aio-claude-toolkitWrote 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/skills/aiocean/claude-plugins/aio-feedback)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-feedback"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-feedback/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-feedback"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-feedback.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00584 |
| Opus 5.5 | $0.00010 | $0.00234 |
| Sonnet 5.5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
aio-feedback 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 1mo 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.
What it actually says
Feedback — Submit Issues for aiocean Plugins
Environment
- gh: !
which gh 2>/dev/null || echo "NOT INSTALLED — brew install gh" - gh auth: !
gh auth status 2>/dev/null | grep -q "Logged in" && echo "authenticated" || echo "NOT AUTHENTICATED — run: gh auth login" - Scripts: !
echo "${CLAUDE_PLUGIN_ROOT}/skills/aio-feedback/scripts"
Submit bug reports, feature requests, and plugin requests directly to the aiocean/claude-plugins repository without leaving Claude Code.
SCRIPTS="${CLAUDE_PLUGIN_ROOT}/skills/aio-feedback/scripts"
Workflow
Step 1: Determine Feedback Type
Ask the user what kind of feedback they want to submit:
| Type | Label | Use for |
|---|---|---|
bug |
bug | Something broken or not working as expected |
feature |
enhancement | Improvement to an existing plugin |
plugin-request |
plugin-request | Request for a new plugin to be added |
Step 2: Collect Details
Gather from the user:
For bug reports:
- Which plugin is affected
- What happened vs what was expected
- Steps to reproduce (if possible)
For feature requests:
- Which plugin (or general marketplace)
- What they want and why
For plugin requests:
- What the plugin should do
- Example use cases
Step 3: Format and Submit
Build a markdown body and submit using the script:
bash "$SCRIPTS/feedback-submit.sh" "<type>" "<title>" "<body>"
Bug report body template:
## Plugin
<plugin-name>
## What happened
<description>
## Expected behavior
<expected>
## Steps to reproduce
<steps or "N/A">
Feature request body template:
## Plugin
<plugin-name or "marketplace">
## What I'd like
<description>
## Why
<motivation>
Plugin request body template:
## Proposed plugin
<name>
## What it should do
<description>
## Use cases
<examples>
Step 4: Confirm
The script outputs the created issue URL. Share it with the user so they can track their feedback.
What ships with it
1 file beside SKILL.md 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.
- 1mo ago First seen · 102 lines · 26 tokens per session scan A 660da5429a82
aio-feedback is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 584 once invoked, about $0.0001 per session on Opus 5.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-08-31.
Other skills, from other repositories
eval-hooks
Audit Claude Code and Codex hooks for validity, safety, and correctness across settings.json, hooks.json, config.toml, plugin, and skill or agent frontmatter hooks. Resolves each command, checks event names, handler types, matchers, exit-code and JSON decision strategy, and timeouts against each host's documented…
eval-skills
Audit a project or library of skills for metadata, trigger boundaries, workflow completion criteria, local resource closure, instruction economy, tool scope, effort, and routing evidence. Use before shipping skills, after importing a skill collection, or when a skill triggers too often or not at all.
source-command-audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
eval-agents
Audit custom subagent definitions for Claude Code (.claude/agents/.md) and Codex (.codex/agents/.toml): loadability against the native schema, description overlap, model tier, tool scope, and headless-safe instructions. Use when onboarding to a project with agents, after adding or importing agents, or when the parent…