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/teloset/telodocs/agents-mdgit clone --depth 1 https://github.com/teloset/telodocsWrote 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/teloset/telodocs/agents-md)<a href="https://agentmods.dev/instructions/teloset/telodocs/agents-md"><img src="https://agentmods.dev/badge/instructions/teloset/telodocs/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 | $0.00871 | $0.00871 |
| Opus 5 | $0.00436 | $0.00436 |
| Sonnet 5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
telodocs 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 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI coding agents working on the telodocs npm package (server, CLI, and scaffold template).
User-facing documentation projects scaffolded via telodocs new include their own AGENTS.md with content-authoring guidance — see template/AGENTS.md.
Setup commands
- Install dependencies:
npm install - Build:
npm run build - Run tests:
npm test - Local CLI (after build):
node dist/cli/index.js new my-docs --no-git
Project layout
| Path | Purpose |
|---|---|
src/cli/ |
CLI commands (new, dev, start) |
src/server/ |
NestJS server — docs API, MCP, search, auth |
src/web/ |
React docs UI (Vite, feature-based, React Query) |
template/ |
Files copied by telodocs new (docs-only scaffold) |
test/ |
Vitest tests |
Scaffolded projects contain docs/, .env, .env.example, .gitignore, README.md, and AGENTS.md.
Code conventions
- TypeScript strict mode; NestJS module/service/controller patterns under
src/server/ - Keep files under ~200 lines where practical — split into focused services
- Match existing naming:
*.service.ts,*.controller.ts,*.module.ts - Run
npm testbefore finishing; fix failures
Changing the scaffold
When editing template/:
- Update
SCAFFOLD_ENTRIESinsrc/cli/commands/new.tsif adding new top-level scaffold files - Update
test/cli/new.spec.tsif scaffold shape changes - Rebuild and run the CLI scaffold test
Documentation authoring instructions for end users live in template/AGENTS.md and template/docs/.
Releases
telodocs is published to npm. Treat every merged change as a release unless the user explicitly says not to bump.
Version bump (required on every change)
- Bump
versioninpackage.json - Keep
package-lock.jsonroot/packages[""]version in sync (runnpm installif needed — it rewrites a stale lockfile version) - Prefer patch for incremental fixes/features (
0.4.0→0.4.1); use minor / major when the change warrants it - Include the bump in the same PR as the change
- Commit message style:
Release vX.Y.Z with <short summary>.
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 · 85 lines · 871 tokens per session scan A a440eeee895f
telodocs AGENTS.md is an instructions file published in the GitHub repository teloset/telodocs (0 stars, last pushed 1mo ago), licensed MIT. It adds 871 tokens to every session, about $0.0044 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.