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 triagegit 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/triage)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/triage"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/triage/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/triage"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/triage.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.00053 | $0.00748 |
| Opus 5 | $0.00026 | $0.00374 |
| Sonnet 5 | $0.00011 | $0.00150 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
triage 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 12d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
triage
Adapted from Matt Pocock's triage. Each issue moves through a series of roles, each with a narrow question. The agent embodies one role at a time and answers only that role's question.
Roles (state machine)
INBOX
→ REPRODUCER (can we reproduce it? if a bug)
→ SCOPER (what's the smallest fix? what's out of scope?)
→ PRIORITIZER (how important is this relative to what's open?)
→ ASSIGNER (who picks this up? agent or human?)
→ READY
Or for non-bug work:
INBOX
→ CLARIFIER (is the user-visible outcome described concretely?)
→ SCOPER (smallest delivering this outcome?)
→ PRIORITIZER (relative importance)
→ ASSIGNER
→ READY
Each role is a focused pass. Don't try to do all of them at once.
Per-role questions
REPRODUCER (bugs only)
- Is there a repro? If not, what's the smallest probable repro?
- Run it (or dispatch a
shellsubagent to). Confirm or refute. - If unreproducible, label
needs-reproand pause until more info.
CLARIFIER (non-bug)
- Is the user-visible outcome described concretely enough that a test could be written for it?
- If no, draft 1–3 questions for the issue author. Don't proceed until answered.
SCOPER
- What's the smallest, well-bounded change that resolves this?
- What's explicitly out of scope?
- Can it be a single slice in a adam flow, or does it want a PRD?
PRIORITIZER
- Compare to other open issues (read titles, not bodies).
- Output one of:
now,next,someday. Avoid finer granularity unless the team has a labelling convention.
ASSIGNER
- Could a Composer 2 subagent do this? Check the slice's clarity and scope.
- If yes → label
agent-ready, ready forslice-to-tasks+ dispatch. - If no → assign to a human, with a one-paragraph note explaining what makes it human-only.
Label vocabulary
Use the project's labels from adam.json (or equivalent). If absent, ask the user once and store them.
Workflow
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.
- 12d ago First seen · 80 lines · 53 tokens per session scan A eebb1307ddb2
triage is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 53 tokens to every session and 748 once invoked, about $0.0003 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.