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 instructions/hyperherox/user-feedback-web/code-qualitygit clone --depth 1 https://github.com/HyperHeroX/user-feedback-webWhat 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 | $0.00373 | $0.00373 |
| Opus 5 | $0.00187 | $0.00187 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
code-quality-standards 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 yesterday.
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
程式碼品質規範
禁止事項
- ❌ 不要添加多餘註解 - 不增加人類不會添加或與文件其餘部分風格不一致的註解
- ❌ 不要過度防禦性編碼 - 不在已驗證路徑添加不必要的 try/catch 區塊或防禦性檢查
- ❌ 不要強制轉型繞過類型問題 - 不為了解決類型錯誤而進行不安全的強制轉換
- ❌ 不要破壞程式碼風格一致性 - 不提交與當前文件風格不一致的程式碼
Commit 前置檢查
進行任何 Git Commit 之前，必須確認以下所有條件均已達成：
- ✅ 編譯無錯誤 - 後端
dotnet build和前端npm run build均成功 - ✅ 單元測試無錯誤 - 所有後端單元測試通過
- ✅ 前端 UI 測試無錯誤 - 前端元件測試通過
- ✅ 瀏覽器 UI 測試無錯誤 - 使用 Browser Automation Tools 進行 E2E 測試
測試要求
- 所有前端/瀏覽器測試必須使用 "Browser Automation Tools"
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.
- yesterday First seen · 28 lines · 373 tokens per session scan A 1631e2963724
code-quality-standards is an instructions file published in the GitHub repository HyperHeroX/user-feedback-web (0 stars, last pushed 4mo ago), licensed MIT. It adds 373 tokens to every session, about $0.0019 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-31.
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.
buildNext
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
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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
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.
langchain 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.