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 shipgit 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/ship)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/ship"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/ship/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/ship"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/ship.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.00042 | $0.00332 |
| Opus 5.5 | $0.00017 | $0.00133 |
| Sonnet 5.5 | $0.00008 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade B, and why
ship scanned grade B with 1 finding 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
description: Commit and push current workspace changes with safe git defaults. Use when they say ship, commit, commit and push, or save this. Follow this skill yourself — never tell them to type /ship. What it actually says
ship
Commit + push with safe defaults. On Codex / ChatGPT, natural language (“commit this”) is the trigger.
Before any git write
git status+git diff— show what will ship.- Never commit secrets (
.env, credentials) — warn and exclude. - Never force push to main/master.
- Never
--no-verifyunless user explicitly asked. - Push only when user said push / ship all / push everything.
Branch rules
| Context | Branch |
|---|---|
| Slice work | adam/<slice-id> per folder contract |
main |
merge only when user explicitly approved |
Respect adam.json → auto_merge_to_main.
Commit message
1–2 sentences, why not what:
git commit -m "$(cat <<'EOF'
Why this change matters.
EOF
)"
Procedure
- Stage relevant files only (unless user said all).
- Commit.
git push -u origin HEADwhen push requested.git statusafter — confirm clean or report remainder.
Scope
Current workspace root. Multi-repo: user names each repo or runs /ship per repo.
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 · 51 lines · 42 tokens per session scan B ae7554885bf5
ship is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (14 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 332 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…