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/agents-mdgit 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.01370 | $0.01370 |
| Opus 5 | $0.00685 | $0.00685 |
| Sonnet 5 | $0.00274 | $0.00274 |
| Haiku 4.5 | $0.00137 | $0.00137 |
Grade A, and why
user-feedback-web AGENTS.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 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Instructions
These instructions are for AI assistants working in this project.
Always open @/openspec/AGENTS.md when the request:
- Mentions planning or proposals (words like proposal, spec, change, plan)
- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
- Sounds ambiguous and you need the authoritative spec before coding
Use @/openspec/AGENTS.md to learn:
- How to create and apply change proposals
- Spec format and conventions
- Project structure and guidelines
Keep this managed block so 'openspec update' can refresh the instructions.
🚨 Non-Negotiable 核心指令
0.強制優先使用Skills進行開發
- 所有開發必須優先使用Skills進行開發
- 僅當Skills無相關可用工具時，才可嘗試其他工具
1. 強制使用 Serena MCP 工具進行原始碼探索
- 所有源代碼探索和分析必須優先使用 Serena MCP 工具箱
- 僅當 Serena MCP 無相關可用工具時，才可嘗試其他工具
- 優先使用符號管理工具而非直接讀取完整檔案
- 使用
get_symbols_overview獲取檔案結構概覽 - 使用
find_symbol進行精確的符號查詢 - 使用
search_for_pattern進行模式搜尋 - 每次新任務開始使用
/speckit.implement進行結構化開發
2. 任何詢問與報告之前都必須使用 User Feedback 通知並等待回應
重要：在提交任何詢問、報告或建議前，必須使用 mcp_user-feedback_collect_feedback 工具通知用戶並等待回應
當User Feedback無法使用時，請使用相關MCP重新啟動工具
適用場景：
- 源代碼修改建議
- 架構變更方案
- API 設計改進
- 效能優化建議
- 安全性改進方案
- 任何可能影響現有功能的改動
- 重大進度（里程碑或任務完成）
- 遇到攔截者或錯誤
- 需要用戶決策或澄清
3. 通訊協議: MCP 專用且必須嚴格遵守
- 所有通訊必須獨家使用 user feedback MCP
- 必須確認通道是 MCP 後再進行任何輸出
- 中間步驟應靜默執行，不報告
4. 自主工作流: 持續執行
- 發送 MCP 後，收到 'continue' 或類似命令時立即恢復任務
- 只有明確指示暫停時才中斷
- 任務完成且無報告條件時自動進行下一個任務
- 任務完成後立即開始下一個待辦項，除非遇到攔截者
5. 行動導向: 立即行動
- 收到 user feedback MCP 回復後立即執行具體任務相關行動
- 每次用戶 MCP 回復後，必須在發送下一個 MCP 前執行至少一個代碼倉庫操作
- 確保每次交換都有具體進度
6. Commit 前置檢查 (必須全部通過)
進行任何 Git Commit 之前，必須確認以下所有條件均已達成：
- ✅ 版本號必須增加 - 每次簽入必須增加版本尾號（patch version），例如
2.6.0→2.6.1 - ✅ 更新 pnpm-lock.yaml - 修改
package.json版本後，必須執行pnpm install --lockfile-only更新 lockfile，否則 CI 會因--frozen-lockfile失敗 - ✅ 編譯無錯誤 - 後端
dotnet build和前端npm run build均成功 - ✅ 單元測試無錯誤 - 所有後端單元測試通過
- ✅ 前端 UI 測試無錯誤 - 前端元件測試通過
- ✅ 瀏覽器 UI 測試無錯誤 - 使用 Browser Automation Tools 進行 E2E 測試
- ✅ Jest 測試無異步洩漏 - 測試完成後不得出現
Jest did not exit one second after the test run has completed警告，若出現必須立即修復
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 · 99 lines · 1,370 tokens per session scan A 3f59267d10fc
user-feedback-web AGENTS.md is an instructions file published in the GitHub repository HyperHeroX/user-feedback-web (0 stars, last pushed 4mo ago), licensed MIT. It adds 1,370 tokens to every session, about $0.0068 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.
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
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
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
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.