Borrowing it
Nothing to install: this file belongs to leetwito/cc-htmlfeedback. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/leetwito/cc-htmlfeedback/main/CLAUDE.mdgit clone --depth 1 https://github.com/leetwito/cc-htmlfeedbackWrote 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/instructions/leetwito/cc-htmlfeedback/claude-md)<a href="https://agentmods.dev/instructions/leetwito/cc-htmlfeedback/claude-md"><img src="https://agentmods.dev/badge/instructions/leetwito/cc-htmlfeedback/claude-md.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.01312 | $0.01312 |
| Opus 5 | $0.00656 | $0.00656 |
| Sonnet 5 | $0.00262 | $0.00262 |
| Haiku 4.5 | $0.00131 | $0.00131 |
Grade A, and why
cc-htmlfeedback CLAUDE.md 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc-htmlfeedback
This repo is the runtime tooling for the cc-htmlfeedback live-feedback loop:
server.js (serves the user's app with the feedback widget injected), lib/ (inject, queue,
watch-inbox helpers), and extension/feedback-widget.js (the widget itself, built via build.js).
The skill ships as a bundled plugin in this repo
This repo is both a Claude Code plugin marketplace and the single source of truth for the
/cc-htmlfeedback skill. Layout:
.claude-plugin/marketplace.json ← marketplace (lists the one plugin)
plugins/cc-htmlfeedback/ ← the installable plugin
.claude-plugin/plugin.json
skills/cc-htmlfeedback/ ← canonical skill source — EDIT HERE
SKILL.md task-workflow.md judge-prompt.md
server.js lib/ feedback-widget.js ← assembled by `node build.js` (do NOT hand-edit)
Edit the skill in plugins/cc-htmlfeedback/skills/cc-htmlfeedback/. The skill resolves its
tooling via TOOLING = ${CLAUDE_PLUGIN_ROOT} (the installed plugin dir), so it works on any
machine with no absolute paths.
server.js + lib/ stay canonical at the repo root (where npm run serve/test point).
node build.js mirrors them - plus the built widget - into plugins/cc-htmlfeedback/ so the
plugin is self-contained. Those plugin copies are build artifacts: never edit them directly,
and run build.js after changing the server, lib, or widget. node build.js --check flags drift.
Install / use
/plugin marketplace add leetwito/cc-htmlfeedback # or: /plugin marketplace add . (local dev)
/plugin install cc-htmlfeedback@cc-htmlfeedback
/cc-htmlfeedback
After editing the skill text, run /plugin marketplace update to refresh the installed copy.
Architect review backlog — TODO (review: 2026-06-18)
Known issues from a four-agent architect review (server/lib, widget/extension, skill/integration, root layout). These are meant to be fixed over time. Re-verify a finding before acting (code moves).
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 · 89 lines · 1,312 tokens per session scan A b94c144a3a93
cc-htmlfeedback CLAUDE.md is an instructions file published in the GitHub repository leetwito/cc-htmlfeedback (13 stars, last pushed 2mo ago), licensed MIT. It adds 1,312 tokens to every session, about $0.0066 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.