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/sayantan94/appliedin/agents-mdgit clone --depth 1 https://github.com/sayantan94/AppliedInWrote 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/sayantan94/appliedin/agents-md)<a href="https://agentmods.dev/instructions/sayantan94/appliedin/agents-md"><img src="https://agentmods.dev/badge/instructions/sayantan94/appliedin/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.03523 | $0.03523 |
| Opus 5 | $0.01761 | $0.01761 |
| Sonnet 5 | $0.00705 | $0.00705 |
| Haiku 4.5 | $0.00352 | $0.00352 |
Grade A, and why
AppliedIn 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 4d 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 -s -o /dev/null -w "%{http_code}\n" http://127.0.0.1:8787/ How it starts
The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on AppliedIn
For anyone changing this code, human or agent. The README covers installing and using it; this covers where things live, how to extend them, and the failures that are expensive to rediscover.
Asked to set it up and start the server? Go straight to Setup. It is scripted end to end; the only things you need from the human are an API key, a résumé and a company or two.
The one rule that outranks the rest: an application is sent under a real person's name and cannot be recalled. A missed application costs an opportunity. A wrong one costs credibility. When a change trades safety for throughput, it is the wrong change.
Setup: "set this repo up and start the server"
This is the most common thing you will be asked, and it is fully scripted, so follow it rather than improvising. Work through the steps in order and verify each one before the next. Do not run them all at once and hope.
Steps 3 to 5 need things only the human has: an API key, their résumé, and which companies they care about. Ask for those. Never invent them, and never write a key into a file you have not read first.
There is exactly one entry point, ./appliedin. If you find yourself reaching for
another script, you are looking at stale instructions.
1. Install
./appliedin setup
Installs uv, Python 3.12, the dependencies, Redis (queues and runtime flags) and Tectonic (renders the résumé PDF). Idempotent, so re-running is safe.
./appliedin is the only entry point. start runs this for you when the
dependencies have moved, so this step is really just "get it wrong early rather
than at launch".
Verify: .venv exists and redis-cli ping answers PONG.
2. Confirm what actually submits applications
command -v claude
Applications are filled in by a claude --chrome subprocess driving the human's
own Chrome. That needs the Claude Code CLI and a Claude subscription; it
refuses API-key auth. Discovery, scoring and tailoring all work without it, so
this is a warning rather than a blocker. Say which of the two situations they are
in rather than letting them find out at the first apply.
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.
- 4d ago First seen · 343 lines · 3,523 tokens per session scan A a52676308e00
AppliedIn AGENTS.md is an instructions file published in the GitHub repository sayantan94/AppliedIn (6 stars, last pushed yesterday), licensed MIT. It adds 3,523 tokens to every session, about $0.0176 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
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.