Borrowing it
Nothing to install: this file belongs to karthikrshet/Career-Agents. 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/karthikrshet/Career-Agents/main/AGENTS.mdgit clone --depth 1 https://github.com/karthikrshet/Career-AgentsWrote 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/karthikrshet/career-agents/agents-md)<a href="https://agentmods.dev/instructions/karthikrshet/career-agents/agents-md"><img src="https://agentmods.dev/badge/instructions/karthikrshet/career-agents/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.00609 | $0.00609 |
| Opus 5 | $0.00304 | $0.00304 |
| Sonnet 5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
Career-Agents 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 8d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Career-Agents AI Contributor Guide
Welcome, AI Contributor! This guide is designed for Claude Code, OpenAI Codex, Cursor, Gemini CLI, Windsurf, Aider, and other AI coding assistants. Follow these guidelines strictly to ensure your edits are successful and preserve registry integrity.
Pre-Development Checklist
Before making any changes to the codebase, prompts, or configurations:
-
Validate Current State Ensure the existing repository is clean and passes all validation checks:
python scripts/validate.py -
Generate Database & Index Maps Compile all schema indexes to verify the workspace is in sync:
python scripts/generate-data.py -
Review Registry Schemas & Mappings Read and understand the following configuration/database files to locate registry structures:
Strict Rules for AI Agents
To avoid registry corruption, broken references, or validation failures, you must adhere to these rules:
- Never Create Duplicate IDs: When adding elements, verify that the new ID is unique across agent-registry.json.
- Never Leave Orphaned Agents: When registering an agent, ensure it exists in both agent-registry.json (under
agents) and divisions.json (in its matching division'sagentsarray). - Never Break Registry Integrity: Do not delete registry entries that are referenced by other entities (e.g. workflows recommending specific agent IDs).
- Never Edit Generated Files Directly: Do not write edits directly to:
career-agents.jsonsearch-index.jsonknowledge-graph.jsonREADME.md(always editscripts/generate-data.py's template instead)- Maps (
agent-map.json,workflow-map.json,company-map.json,career-path-map.json) - LLM text lists (
llms.txt,llms-full.txt,career-agents-index.json)
- Always Regenerate After Changes: After modifying any agent files, workflows, divisions, companies, or career paths, you must run:
python scripts/generate-data.py
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.
- 8d ago First seen · 65 lines · 609 tokens per session scan A 5e14bf7446b8
Career-Agents AGENTS.md is an instructions file published in the GitHub repository karthikrshet/Career-Agents (39 stars, last pushed yesterday), licensed MIT. It adds 609 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-30.
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
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.