Borrowing it
Nothing to install: this file belongs to bensyverson/jobs. 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/bensyverson/jobs/main/AGENTS.mdgit clone --depth 1 https://github.com/bensyverson/jobsWrote 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/bensyverson/jobs/agents-md)<a href="https://agentmods.dev/instructions/bensyverson/jobs/agents-md"><img src="https://agentmods.dev/badge/instructions/bensyverson/jobs/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.04461 | $0.04461 |
| Opus 5 | $0.02230 | $0.02230 |
| Sonnet 5 | $0.00892 | $0.00892 |
| Haiku 4.5 | $0.00446 | $0.00446 |
Grade A, and why
jobs 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 7d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT: As you implement features, keep the documentation up to date; update README.md only when a doc file is added or new users must know.
Overview
You are working on Jobs, a hierarchical task manager for the CLI, backed by an event store in SQLite.
Documentation
- docs/content/docs/ — the published documentation site (Hugo);
make docsserves it locally - DOCS.md — the full CLI reference; the fastest way to learn what a command does
- README.md — what Jobs is and a quick start, written for humans
- DESIGN.md — the dashboard's design system: tokens, type scale, component specs
- project/ — dated design documents and agent-feedback reports; project/gotchas.md holds project traps and rule feedback
- Makefile —
build,install,test,test-js, and the docs targets - scripts/ — re-runnable tooling (screenshots, snapshot replay, getting-started verification)
Architecture
internal/job is the product — the SQLite event store, the plan grammar, and the rendering. cmd/job is a thin cobra CLI over it, and internal/web is a server-rendered dashboard over the same core.
- Schema changes are numbered migrations in internal/migrations/. They are applied when the database is opened, so any
jobinvocation migrates — there is no server to restart. - DESIGN.md is the design system the web rules below defer to, authoritative for everything under
internal/web/— including its desktop-first density target, which outranks the web rules' mobile-first default. The dashboard is localhost-only and read-only, so the rule about public-page<head>metadata does not apply here. - The dashboard's JS is mostly plain progressive-enhancement modules in
internal/web/assets/js/, not custom elements; onlypeek-sheetandlive-regionare registered, and neither uses a shadow root. The web rules' one-element-per-file-with-a-shadow-root convention governs new components — don't retrofit the existing scripts to it as a side quest. - This repo builds
job. Thejobon yourPATHand the./jobat the repo root are both stale untilmake install/make build, so a CLI change you just wrote is not exercised by runningjobuntil you rebuild.
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.
- 7d ago First seen · 166 lines · 4,461 tokens per session scan A 41b3a4545cf1
jobs AGENTS.md is an instructions file published in the GitHub repository bensyverson/jobs (24 stars, last pushed 4d ago), licensed MIT. It adds 4,461 tokens to every session, about $0.0223 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.