Borrowing it
Nothing to install: this file belongs to gurdasnijor/server-quality-harness. 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/gurdasnijor/server-quality-harness/main/AGENTS.mdgit clone --depth 1 https://github.com/gurdasnijor/server-quality-harnessWrote 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/gurdasnijor/server-quality-harness/agents-md)<a href="https://agentmods.dev/instructions/gurdasnijor/server-quality-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/gurdasnijor/server-quality-harness/agents-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.03841 | $0.03841 |
| Opus 5 | $0.01920 | $0.01920 |
| Sonnet 5 | $0.00768 | $0.00768 |
| Haiku 4.5 | $0.00384 | $0.00384 |
Grade A, and why
server-quality-harness AGENTS.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "http://127.0.0.1:8081/mcp?debug=true" \ Copies of this mod
1 near-identical copy found in the catalogue:
- my-smithery-app AGENTS.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 494 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Welcome to the Smithery TypeScript MCP Server Scaffold!
This is the template project that gets cloned when you run npx create-smithery. It provides everything you need to build, test, and deploy a Model Context Protocol (MCP) server with Smithery.
Table of Contents
- Project Structure
- Quick Start Commands
- smithery.yaml Configuration
- Concepts
- Development Workflow
- Deployment & CI/CD
- Troubleshooting
- Resources
- Community & Support
Project Structure
your-server/
├── package.json # Project dependencies and scripts
├── smithery.yaml # Runtime specification (runtime: typescript)
├── src/
│ └── index.ts # Main server implementation
└── README.md
Quick Start Commands
# Run development server (streamable HTTP on port 8081)
# Opens interactive Smithery playground in your browser for testing
npm run dev # or: bun run dev, pnpm run dev, yarn dev
# Run on a custom port
npm run dev -- --port 3000
# Kill existing process if port 8081 is in use
lsof -ti:8081 | xargs kill
# Build for production
npm run build # or: bun run build, pnpm run build, yarn build
smithery.yaml Configuration
The smithery.yaml file configures how your server runs. For this TypeScript setup, it only needs:
Required Field
runtime: typescript
This tells Smithery to use the TypeScript runtime for your server.
Optional Fields
target (optional)
Specifies where your server runs and determines the transport protocol. Can be local or remote:
runtime: typescript
target: remote # Options: remote (default) or local
local: Server runs on the user's machine using stdio transport. When published, bundled into.mcpbfile for distributionremote: Server runs on Smithery's infrastructure using HTTP transport (default)
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 · 494 lines · 3,841 tokens per session scan A f8b0c4954bb3
server-quality-harness AGENTS.md is an instructions file published in the GitHub repository gurdasnijor/server-quality-harness (0 stars, last pushed 10mo ago), licensed ISC. It adds 3,841 tokens to every session, about $0.0192 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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.
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).
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).
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.
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.