What is AppliedIn CLAUDE.md?

Repository instructions for AppliedIn, including where to find the main development rules and how to set up and run the application. AppliedIn is a browser-based job-application tool, based on the described workflow.

Starting the server, changing source or browser files, debugging the browser agent, and adding job preferences or site-specific instructions.

They keep changes aligned with the repository's setup process and emphasize checking each step before sending an application under a real person's name.

How sayantan94/AppliedIn configures Claude Code

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/CLAUDE.md

Clone the repo

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

Made for: Claude Code.

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/claude-md/github.svg)](https://agentmods.dev/instructions/sayantan94/appliedin/claude-md)

Your own site

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

Per session 525 This file is loaded in full into every session.

When invoked 525 The same file — it is already loaded in full.

Security scan A 0 findings. 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.00525	$0.00525
Opus 5.5	$0.00210	$0.00210
Sonnet 5.5	$0.00105	$0.00105
Haiku 4.5	$0.00052	$0.00052

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

Security

Grade A, and why

AppliedIn CLAUDE.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 2mo 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.

CLAUDE.md · 44 lines

How it starts

The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Read AGENTS.md before changing anything. It is the guide for working on this repo: layout, how to add a job preference or a per site playbook, how to debug the browser agent, and the invariants that must stay enforced in code.

Everything in this file is a pointer to that one. If the two ever disagree, AGENTS.md is right.

If you are asked to set this repo up and start the server, follow AGENTS.md → Setup exactly. It is scripted end to end through a single entry point, ./appliedin. Ask the human for the three things only they have (an OpenAI key, their résumé at resume/base.tex, and a company or two to watch) rather than inventing values, and verify each step before moving to the next.

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

Before you start

Restart the daemon after any src/ change. There is no hot reload, and the browser caches web/app.js and web/styles.css, so a UI change needs a hard reload as well. Testing stale code has wasted more time here than any bug.
Run the tests: .venv/bin/python -m pytest -q. They are offline by design; never add one that reaches the network or drives a browser.
Diagnose with evidence, not theory. The worst bug in this repo's history was guessed at three times and solved once, by reading the browser session's own report instead of its one line verdict. AGENTS.md has the drill.

Do not

Move a guard from code into a prompt. The invariants in AGENTS.md hold because the tool layer enforces them regardless of what the model emits.
Commit .local/, resume/base.tex or anything under output/. They hold real personal data. config/watchlist.yaml and config/preferences.yaml are tracked, so treat them as public.
Add a preference field to the interface without wiring it into discovery/relevance.py. A setting nothing reads is a lie.

Read the full file on GitHub · 44 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.

2mo ago First seen · 44 lines · 525 tokens per session scan A 87384288e0a5

Subscribe to this mod's changes

AppliedIn CLAUDE.md is an instructions file published in the GitHub repository sayantan94/AppliedIn (8 stars, last pushed 13d ago), licensed MIT. It adds 525 tokens to every session, about $0.0021 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-08-31.

AppliedIn CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
AppliedIn CLAUDE.mdsayantan94/AppliedIn	Instructions file	8	13d ago	MIT	A	525	Claude Code
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 Claude Code