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 skills add corezoid/corezoid-ai-plugin --skill corezoid-feedbackgit clone --depth 1 https://github.com/corezoid/corezoid-ai-pluginWrote 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/corezoid/corezoid-ai-plugin/corezoid-feedback)<a href="https://agentmods.dev/skills/corezoid/corezoid-ai-plugin/corezoid-feedback"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-feedback.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.00231 | $0.01022 |
| Opus 5 | $0.00115 | $0.00511 |
| Sonnet 5 | $0.00046 | $0.00204 |
| Haiku 4.5 | $0.00023 | $0.00102 |
Grade A, and why
corezoid-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 7d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corezoid Feedback Skill
You help users report bugs, suggest improvements, and flag unexpected behavior in the Corezoid plugin to the Corezoid team.
When to offer and how to phrase it
Case 1 — bug or broken behavior. The user reports something that stopped working, produced wrong output, or broke their process. Offer once, adapting to the context:
"Хотите сообщить о баге команде Corezoid?"
Case 2 — improvement request. The user hints that something could work better ("хотелось бы", "было бы здорово", "можно улучшить"):
"Хотите отправить пожелание команде Corezoid?"
Case 3 — platform-level mistake by the plugin. The message reveals that the plugin chose the wrong node type, wrong API, wrong structure, or wrong MCP tool. Add one line to the normal response without interrupting it:
"Хотите сообщить об этом команде Corezoid?"
In all cases: offer once per problem context, do not repeat if the user declines. Do not offer when the user is iterating on business logic.
What to collect
If the user agrees, derive as much as possible from context and ask only for what is missing:
| Field | Meaning |
|---|---|
problem (required) |
What went wrong, in the user's words |
expected |
What the user expected to happen |
proposed_solution |
How the user thinks it should work |
tool |
Which tool or skill was involved (derive from context) |
transcript_excerpt |
Short relevant excerpt of the dialog |
contact |
Optional email or handle for follow-up |
Mandatory confirmation step
Before calling send-feedback, always show the user exactly what will be sent:
Планирую отправить следующее:
• Проблема: <problem text>
• Ожидалось: <expected text>
• Предложение: <proposed_solution text>
• Инструмент: <tool>
• Выдержка из диалога: <transcript_excerpt>
• Контакт: <contact or "не указан">
Explicitly note that any tokens, API keys, and secrets have been masked. Ask the user to confirm, edit, or cancel before proceeding.
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.
- 7d ago First seen · 111 lines · 231 tokens per session scan A a852cfdb9e29
corezoid-feedback is a skill published in the GitHub repository corezoid/corezoid-ai-plugin (73 stars, last pushed 2d ago), licensed MIT. It adds 231 tokens to every session and 1,022 once invoked, about $0.0012 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-08-30.
Other skills, from other repositories
stop-that-shit
Keep coding agents focused on requested and necessary work. Use when a request sets a read-only, answer-only, file, action, or stopping boundary; when evidence shows scope creep, speculative hardening, unnecessary hashing or dependencies, repeated audit loops, or valueless delegation; or when the user invokes Stop…
stss
Reduce defensive disclaimers, stacked hedging, and self-protective narration in proposals and decision-facing writing. Use when the user asks to rewrite or audit a proposal, plan, research contribution, executive summary, or similar text for directness. Do not use for ordinary code work or unrelated prose.
superloopy-clone
Use when the user asks for Superloopy clone or asks to clone, rebuild, reverse-engineer, replicate, or copy a website or page into a Superloopy-governed implementation. Triggers on "loopy clone", target URLs plus requests such as "clone this site", "rebuild this page", "make a copy of this website", "pixel-perfect…
superloopy-loop
Use Superloopy's lightweight strict-evidence loop for Codex tasks that need durable progress, criteria, and artifact-backed completion.
superloopy-doctor
Use when diagnosing Superloopy doctor, install, wrapper, plugin cache, hook bootstrap, bundled agents, marketplace, Codex, Claude Code, stale-version, evidence-floor, or host-wiring health problems.
inspect-codex-trajectory
Inspect or show a local Codex task trajectory, including turns, approximate model steps, assistant messages, reasoning summaries, tool calls, failures, compaction, token usage, and timing. Use when the user asks for a trajectory, execution trace, task timeline, slow-tool analysis, visual event ledger, or live…