What is AppliedIn AGENTS.md?

Repository-specific instructions for AppliedIn, an application that submits job applications. They explain setup, where important code lives, and the checks needed before an application is sent under a real person’s name.

Use them when installing AppliedIn, starting its server, finding the application-submission path, handling required credentials and résumé data, and changing the project safely.

They prevent unsafe setup and code changes in a system where a submitted application cannot be recalled. They also make clear which details must come from the user, such as an API key, résumé, and target companies.

How sayantan94/AppliedIn configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to sayantan94/AppliedIn. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/sayantan94/AppliedIn/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/sayantan94/AppliedIn

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/sayantan94/appliedin/agents-md/github.svg)](https://agentmods.dev/instructions/sayantan94/appliedin/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/sayantan94/appliedin/agents-md"><img src="https://agentmods.dev/badge/instructions/sayantan94/appliedin/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/sayantan94/appliedin/agents-md"><img src="https://agentmods.dev/badge/instructions/sayantan94/appliedin/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 3,544 This file is loaded in full into every session.

When invoked 3,544 The same file — it is already loaded in full.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.03544	$0.03544
Opus 5.5	$0.01418	$0.01418
Sonnet 5.5	$0.00709	$0.00709
Haiku 4.5	$0.00354	$0.00354

Measured 1mo ago against content hash b1105753bb62, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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/

AGENTS.md · 344 lines

How it starts

The opening of the file, as written. The whole thing — 344 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.

Read the full file on GitHub · 344 lines

Changes

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.

1mo ago Changed · +1 lines · +21 tokens per session b1105753bb62
2mo ago First seen · 343 lines · 3,523 tokens per session scan A a52676308e00

Subscribe to this mod's changes

AppliedIn AGENTS.md is an instructions file published in the GitHub repository sayantan94/AppliedIn (8 stars, last pushed 13d ago), licensed MIT. It adds 3,544 tokens to every session, about $0.0142 per session on Opus 5.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.

AppliedIn AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
AppliedIn AGENTS.mdsayantan94/AppliedIn	Instructions file	8	13d ago	MIT	A	3,544	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

AppliedIn: Instructions file for Codex