Borrowing it
Nothing to install: this file belongs to engasnm111/lnwjud. 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/engasnm111/lnwjud/main/AGENTS.mdgit clone --depth 1 https://github.com/engasnm111/lnwjudWrote 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/engasnm111/lnwjud/agents-md)<a href="https://agentmods.dev/instructions/engasnm111/lnwjud/agents-md"><img src="https://agentmods.dev/badge/instructions/engasnm111/lnwjud/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/engasnm111/lnwjud/agents-md"><img src="https://agentmods.dev/badge/instructions/engasnm111/lnwjud/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.02529 | $0.02529 |
| Opus 5.5 | $0.01012 | $0.01012 |
| Sonnet 5.5 | $0.00506 | $0.00506 |
| Haiku 4.5 | $0.00253 | $0.00253 |
Grade A, and why
lnwjud 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 24d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository agent instructions
Branch workflow
Do routine development directly on dev. Do not create feature, hotfix, or
codex/* branches, or a new worktree for branch isolation, unless the user
explicitly requests one. Keep main for verified dev -> main merges through
the existing pull-request and branch-protection process; do not develop on
main. After earlier temporary branches are merged and no open pull request or
worktree uses them, remove them so the repository retains only dev and
main. Check for uncommitted work and active ownership before any cleanup.
Automatic scheduled continuation
When a user-authorized repository task is still incomplete and the user has authorized scheduled continuation, load and follow .agents/skills/lnwjud-scheduled-continuation/SKILL.md as the source of truth. Never create a schedule when the user has explicitly opted out for the current task.
For rolling continuation, the workspace skill is authoritative. Current mainline uses exactly one hourly recurring Native ChatGPT Scheduled Task for an active goal, in the current chat with cloud execution requested. Ordinary checkpoints and ordinary recurring wakes reuse the same native task; they do not create or retime a per-turn successor. Historical one-time watchdog rows are compatibility-only. Never use lnwjud scheduler, Windows Task Scheduler, schtasks.exe, cron, shell timers, browser/DOM automation, or undocumented scheduler APIs as a fallback. Never create or re-enable scheduled continuation when the user has explicitly disabled it for the current task.
Scheduled and manual durable workers are work-conserving. Discovering a fixable CI/test/code-scanning/packaging/release/tool failure is the next unit of work, not a status boundary: inspect the exact failure, diagnose it, repair it, and run the relevant validation in the same host turn while safe useful actions remain. Do not spend an hourly wake merely summarizing an intermediate problem that can still be acted on; user-visible status prose never substitutes for available execution.
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.
- 24d ago Changed · +4 lines · +197 tokens per session 8ab46c16ac31
- 25d ago Changed · +7 lines · +84 tokens per session 3319d8a2bc22
- 26d ago Changed · +12 lines · +221 tokens per session 9a2ec78488dd
- 28d ago Changed · +62 tokens per session cc8224b21b37
- 1mo ago Changed · +4 lines · +129 tokens per session f3bb96b28367
- 1mo ago Changed · +15 lines · +427 tokens per session 1c235a563ce0
- 1mo ago Changed · +11 lines · +395 tokens per session 2e213cad7bc1
- 1mo ago First seen · 44 lines · 1,014 tokens per session scan A a878152639cd
lnwjud AGENTS.md is an instructions file published in the GitHub repository engasnm111/lnwjud (205 stars, last pushed today), licensed MIT. It adds 2,529 tokens to every session, about $0.0101 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-09-11.
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).