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/sam3690/hackernews_mcp/copilot-instructionsgit clone --depth 1 https://github.com/sam3690/Hackernews_mcpWhat 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.00592 | $0.00592 |
| Opus 5 | $0.00296 | $0.00296 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
Hackernews_mcp copilot-instructions.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 2d 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
# hn-mcp-server Development Guidelines
Auto-generated from all feature plans. Last updated: 2025-10-12
**⚠️ IMPORTANT**: All development MUST comply with the project constitution at `.specify/memory/constitution.md`
## Constitution Quick Reference
Before starting any work, review these non-negotiable principles:
1. **Code Quality First**: Zero technical debt, full type safety, linting clean
2. **Test-First Development**: TDD mandatory - tests → approval → fail → implement → pass → refactor
3. **UX Consistency**: Follow MCP naming conventions, consistent parameters, clear error messages
4. **Latest Dependencies**: Always use Context7 MCP to retrieve latest docs before using libraries
5. **Documentation-Driven**: Specs written first, API docs complete, examples provided
6. **Integration Testing**: Real API tests, contract validation, error scenario coverage
7. **Observability**: Structured logging, error context, performance metrics, debug mode
## Active Technologies
- TypeScript 5.7+ with Node.js 20 LTS (strict mode enabled) (001-hackernews-mcp-server)
## Project Structure
```
src/
tests/
```
## Commands
npm test [ONLY COMMANDS FOR ACTIVE TECHNOLOGIES][ONLY COMMANDS FOR ACTIVE TECHNOLOGIES] npm run lint
## Code Style
TypeScript 5.7+ with Node.js 20 LTS (strict mode enabled): Follow standard conventions
**Note**: All code style rules must align with "Code Quality First" principle in constitution.
## Recent Changes
- 001-hackernews-mcp-server: Added TypeScript 5.7+ with Node.js 20 LTS (strict mode enabled)
## Development Workflow (Constitution-Aligned)
1. **Before Starting**: Read feature spec, check constitution compliance requirements
2. **Research Phase**: Use Context7 MCP to retrieve latest docs for any external libraries
3. **Test Phase**: Write tests first, get approval, verify they fail
4. **Implementation**: Write code following quality standards, with observability
5. **Validation**: Run all quality gates (linter, types, tests, coverage)
6. **Documentation**: Update API docs, examples, CHANGELOG
7. **Review**: Complete constitution compliance checklist
## Quality Gates (All Must Pass)
- [ ] Linter clean (zero warnings/errors)
- [ ] Type checker passing (strict mode)
- [ ] Tests passing (unit + integration + contract)
- [ ] Coverage ≥80% (no decrease from baseline)
- [ ] Documentation complete
- [ ] Security audit clean (npm audit / pip-audit)
- [ ] Constitution compliance checklist completed
<!-- MANUAL ADDITIONS START -->
<!-- MANUAL ADDITIONS END -->
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.
- 2d ago First seen · 62 lines · 592 tokens per session scan A f2645d59525a
Hackernews_mcp copilot-instructions.md is an instructions file published in the GitHub repository sam3690/Hackernews_mcp (0 stars, last pushed 10mo ago), licensed MIT. It adds 592 tokens to every session, about $0.0030 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
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).
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.
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.
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).
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.