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 to-issuesgit 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/to-issues)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/to-issues"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/to-issues/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/to-issues"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/to-issues.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.00058 | $0.00591 |
| Opus 5 | $0.00029 | $0.00296 |
| Sonnet 5 | $0.00012 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
to-issues 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
to-issues
Adapted from Matt Pocock's to-issues. Cut a plan into work that another engineer (or another subagent) can pick up without asking you anything.
In a adam flow, you'd typically use slice-to-tasks instead — it produces structured slice briefs for Composer 2 dispatch. Use to-issues when the work needs to flow through a real issue tracker (GitHub/Linear) or when humans are picking it up.
Issue tracker selection
Check the project's convention:
- GitHub:
gh issue create. Repo must be on GitHub. - Linear: Linear MCP. Team and project ids needed.
- Local files: write to
docs/issues/<slug>.md.
If unclear, ask the user which one.
Vertical slicing rules
Same as slice-to-tasks:
- Each issue delivers one user-visible behavior or one well-bounded piece of infra.
- Each issue has explicit acceptance criteria, in-scope paths, out-of-scope paths.
- Issues declare their dependencies on each other.
Issue template
## Summary
One paragraph. What this delivers.
## Acceptance criteria
- AC-1: ...
- AC-2: ...
## Paths in scope
- ...
## Paths out of scope
- ...
## Depends on
- #<issue> or <none>
## Notes
Optional. Pointers to similar code, gotchas. Terse.
Workflow
- Read the source (PRD, plan, packet).
- Draft issues in your head. Aim for 3–10. More is a sign of horizontal slicing.
- Create the issues in the chosen tracker with the template below. Default: do not wait for operator approval on the list. Only pause for approval when
require_plan_approval: true. - Record the issue numbers in the source doc (e.g. add a "Tracked in" section to the PRD).
Anti-patterns
- Issues with vague acceptance ("make it work").
- Issues that span the entire codebase ("add caching everywhere").
- Issues with implicit deps. Always state
depends on. - Bulk-creating issues without a quick summary in
scratch/last-run.md(operator can review at handoff, not mid-run).
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 · 69 lines · 58 tokens per session scan A e828821e14af
to-issues is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 58 tokens to every session and 591 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.