Borrowing it
Nothing to install: this file belongs to zvieli/TechJobMCP. 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/zvieli/TechJobMCP/main/AGENTS.mdgit clone --depth 1 https://github.com/zvieli/TechJobMCPWrote 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/zvieli/techjobmcp/agents-md)<a href="https://agentmods.dev/instructions/zvieli/techjobmcp/agents-md"><img src="https://agentmods.dev/badge/instructions/zvieli/techjobmcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/zvieli/techjobmcp/agents-md"><img src="https://agentmods.dev/badge/instructions/zvieli/techjobmcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00413 | $0.00413 |
| Opus 5.5 | $0.00165 | $0.00165 |
| Sonnet 5.5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
TechJobMCP 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 17d 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
TechJobMCP agent instructions
The engineering source of truth is specs/SPEC_PRODUCTION_ENHANCEMENT.md. Read it before planning or editing. Dependency, artifact, and local-state ownership is documented in docs/REPRODUCIBILITY.md. The SPEC takes precedence over milestone summaries and historical test counts.
- Keep the full suite green. Run
uv run pytest tests/before and after a change; record actual passed, xfailed, skipped, and warning counts. Never treat an old count as a test contract. - Use uv exclusively. Manage dependencies with
uv; do not run rawpip, edituv.lockby hand, or install an independent Torch variant outside the project lock. Useuv lock --checkand a locked sync when checking dependency reproducibility. - Preserve the headless MCP boundary. Do not add a product frontend, React app, TUI, or unrelated career features. Tests must be offline, CPU-runnable, and free of paid LLM calls.
- Keep FastMCP sessions safe. Do not alter or bypass the SSE
text/event-streamhandling or Gemini probe headers injob_mcp/main.py. New routes must remain isolated from session checks. - Separate evidence from claims. Do not infer market coverage, posting freshness, employer intent, or unbiased model quality from fixture-only evidence. The M3 and M7 canonical artifacts have separate validators and publication policies.
- Report quality gates honestly. Run scoped Ruff for every new or materially changed Python file. Repository-wide Ruff debt is documented as non-blocking in the SPEC and CI; never describe that check as passing unless it actually does. Run
git diff --checkand the appropriate build/test gates before completion.
For current milestone scope and acceptance criteria, use the authoritative SPEC rather than adding a second roadmap here.
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.
- 17d ago First seen · 13 lines · 413 tokens per session scan A d588d5f8b202
TechJobMCP AGENTS.md is an instructions file published in the GitHub repository zvieli/TechJobMCP (1 stars, last pushed 14d ago), licensed MIT. It adds 413 tokens to every session, about $0.0017 per session on Opus 5.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-10-04.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.