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/tommybez/skillsboard/agents-mdgit clone --depth 1 https://github.com/TommyBez/skillsboardWrote 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/tommybez/skillsboard/agents-md)<a href="https://agentmods.dev/instructions/tommybez/skillsboard/agents-md"><img src="https://agentmods.dev/badge/instructions/tommybez/skillsboard/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.01046 | $0.01046 |
| Opus 5 | $0.00523 | $0.00523 |
| Sonnet 5 | $0.00209 | $0.00209 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
skillsboard 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 yesterday.
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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Cursor Cloud specific instructions
What this is
skillsboard is a single Next.js 16 (App Router, Turbopack) app — UI + API routes in one process. Its backing store is a Neon PostgreSQL database (pulled from Vercel; see below). Auth is Better Auth (email OTP via Resend + organizations + OAuth/MCP provider). There is no separate backend to run.
Running locally
- Environment lives in
.env.local(gitignored, so it is not in the repo). Populate it from Vercel (VERCEL_TOKENis provided as a secret): the project is linked totommasos-projects-bb9d6551/skillsboard. Pull the Development variables (Neon PostgresDATABASE_URL/DATABASE_URL_UNPOOLED,BETTER_AUTH_SECRET,VERCEL_OIDC_TOKEN, etc.) with:npx vercel env pull .env.local --environment=development --yes(runnpx vercel link --yes --project skillsboard --scope tommasos-projects-bb9d6551first if.vercel/project.jsonis absent). This points the app at the persistent Neondevelopmentbranch, isolated from Production'smainbranch. Preview deployments use Neon-managed ephemeral branches. SetBETTER_AUTH_URL=http://localhost:3000in.env.localfor local auth callbacks. PostHog variables are scoped to Vercel Production and analytics is intentionally disabled in local development and Preview deployments. - Dev server:
pnpm dev(serveshttp://localhost:3000). Standard scripts live inpackage.json. - After changing
.env.local, restartpnpm devso thepgpool inlib/db/index.ts(created at module load) picks up the newDATABASE_URL.
Database schema
The schema lives in lib/db/schema.ts and is managed with versioned Drizzle migrations committed in drizzle/ (see docs/database-migrations.md). After editing the schema, run pnpm db:generate --name <description> and commit the generated SQL together with the schema change — do not hand-edit drizzle/meta/. Vercel builds apply pending migrations automatically (vercel-build runs pnpm db:migrate before next build): preview builds against the Neon preview/<git-branch> database branch, production builds against Neon main. Drizzle uses the direct DATABASE_URL_UNPOOLED; the app continues to use pooled DATABASE_URL. To align the database in .env.local (normally the Neon development branch), run pnpm db:migrate. pnpm db:push remains for throwaway prototyping only; never push to a migration-managed database, or the next db:migrate will fail on drift.
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.
- yesterday First seen · 35 lines · 1,046 tokens per session scan A 064c1dc28826
skillsboard AGENTS.md is an instructions file published in the GitHub repository TommyBez/skillsboard (5 stars, last pushed yesterday), licensed MIT. It adds 1,046 tokens to every session, about $0.0052 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-09-03.
Other instructions, from other repositories
lms-front AGENTS.md
AGENTS.md instructions for guillermoscript/lms-front, covering claude.md, project overview, commands, development and database (supabase).
lms-front CLAUDE.md
Claude Code instructions for guillermoscript/lms-front, covering claude.md, project overview, commands, architecture and multi-tenancy.
tutor-management-app AGENTS.md
Instructions for t1112000/tutor-management-app, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
counterpoise-ledger CLAUDE.md
Instructions for jeffjjohnston/counterpoise-ledger, covering claude.md, project overview, development commands, essential commands and testing.
windmill AGENTS.md
AGENTS.md instructions for windmill-labs/windmill, covering windmill, workflow, documentation, dev environment and per-worktree ports and database.
pgroles AGENTS.md
AGENTS.md instructions for thepartly/pgroles, covering agents.md, build & test commands, format + lint (always run before committing), unit tests (no database needed) and integration tests (requires live postgresql).