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 skills add Justinmendezai/The-Adam-Repo --skill whatgit clone --depth 1 https://github.com/Justinmendezai/The-Adam-RepoWrote 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/skills/justinmendezai/the-adam-repo/what)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/what"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/what/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/skills/justinmendezai/the-adam-repo/what"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/what.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.01091 |
| Opus 5.5 | $0.00029 | $0.00436 |
| Sonnet 5.5 | $0.00014 | $0.00218 |
| Haiku 4.5 | $0.00007 | $0.00109 |
Grade A, and why
what 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
what?
Explain mode — not build mode. Turn confusion into calibrated clarity + OSS context agents can reuse.
Before answering
- Read (if present):
adam/context/technical-level.mdadam/context/preferences.md(Teach me / Pair / Just build it)
- If missing → calibrate is incomplete. Answer at beginner + Teach me defaults, then continue calibrate in this chat. Do not tell them to type
/calibrate. - Do not write product code unless user pivots to build.
Calibrated voice (required)
| Level | Words | Structure | OSS research |
|---|---|---|---|
| never coded | No jargon without plain-English gloss; analogies first | Short paragraphs; numbered steps | 1–2 famous OSS products they'd recognize ("like how WordPress…") |
| beginner | Define terms on first use | Bullets; one concept per bullet | 1–2 repos with what to look at (README section, folder name) |
| intermediate | Standard dev vocabulary OK | Pro/con table + when-to-use | 2–3 repos or reference implementations + file paths to skim |
| professional | Terse; no tutorial padding | Bottom line → tradeoffs → links | Best OSS reference + why it matters; skip basics |
Preferences override:
- Teach me → +1 depth level of explanation (never skip "why").
- Just build it → compress to decision summary + links (still run OSS scan if non-obvious).
- Pair with me → middle path; ask one checkpoint question at end.
If never coded and topic involves IDE/git/repo: include a "Where this lives" box (Cursor = the app; repo = project folder; agent = helper in chat).
Workflow
- Restate the user's question in one plain sentence ("You're asking whether…").
- Simplest terms — core idea in 2–4 sentences max before detail.
- Pros / cons / when — markdown table (minimum 2 pros, 2 cons, 1 "use when / skip when").
- Supporting context — only what changes the decision (constraints, common mistakes, related terms).
- OSS research pod (always for non-trivial topics):
- Search for open-source reference implementations, not blog opinions.
- Prefer: active repo, clear README, license compatible with learning, similar problem shape.
- Output Agent context block (below) — paths/links agents should read before implementing.
- Save longer dumps to
scratch/research/what-<slug>-<YYYYMMDD>.mdwhen >15 lines.
- Next step — do it or ask one plain-language question (“Want me to keep going on the first version?”). Never list slash commands.
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 · 103 lines · 72 tokens per session scan A a2ca817b994f
what is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (14 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,091 once invoked, about $0.0003 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.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.