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 paultyng/skill-issue --skill review-trajectorygit clone --depth 1 https://github.com/paultyng/skill-issueWrote 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/paultyng/skill-issue/review-trajectory)<a href="https://agentmods.dev/skills/paultyng/skill-issue/review-trajectory"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/review-trajectory/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/paultyng/skill-issue/review-trajectory"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/review-trajectory.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.00090 | $0.01714 |
| Opus 5.5 | $0.00036 | $0.00686 |
| Sonnet 5.5 | $0.00018 | $0.00343 |
| Haiku 4.5 | $0.00009 | $0.00171 |
Grade A, and why
review-trajectory 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trajectory Review
A review that asks where the codebase is heading, not whether the diff is correct. It counts structural members, checks whether they change together, and reports whether this diff is the point at which consolidation becomes worth doing.
The output is advisory. It never asks for a change to the diff under review.
What makes this review different
Every other reviewer reports defects in changed files. This one reports a count across the whole repository, and the diff that triggers it is usually clean.
A third entrypoint that copies the existing two conforms perfectly. The
conformance check passes it. The minimalism lens finds nothing premature,
because nothing was abstracted. The duplication it adds is an explicit
false-positive guard in review-code/reference-architecture.md. The signal is
the count, and the count is invisible to a reviewer scoped to changed files.
So this reviewer is anti-scoped. It reads the members the diff never touches, because that is the only way to count past one.
Workflow
1. Resolve scope and repository state
- The scope of findings is the whole repository. The diff only decides which axes are worth examining first.
- Get the diff under review:
git diff --name-only --diff-filter=d <base>...HEAD. The default<base>ismain. For a PR number, usegh pr diff <number> --name-only. - Measure repository maturity with the recipe in reference-census-axes.md. Under 90 days of elapsed history is greenfield.
- If the repository has fewer than 2 commits, stop. There is no history.
2. Census
For each axis in the table in reference-census-axes.md, count the members present in the tree at HEAD. Record the member paths, not only the count. The paths are evidence and the report must cite them.
Run the enumeration commands the table gives, and adapt them to the repository's language and layout. Report the command you actually ran.
Skip an axis that has fewer than 2 members.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 167 lines · 90 tokens per session scan A c8b2bcc724db
review-trajectory is a skill published in the GitHub repository paultyng/skill-issue (8 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 1,714 once invoked, about $0.0004 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-10-17.
Other skills, from other repositories
deep-review
Evidence-based deep code review rubric — severity + confidence findings across maintainability, correctness, security, performance, and testing. Push for ambitious structural simplification (code judo), not just local cleanup. Escalate hands-on triage to the code-reviewer agent.
gh-address-comments
Triage and address open GitHub PR review and conversation comments using the gh CLI. Use when the user wants to "address PR comments", "resolve review threads", or "respond to reviewers" on the current branch's pull request.
pr-alignment-loop
Iterate a PR to its final form by running two opposing reviewer droids (reviewer-robustness and reviewer-minimalist) in a bounded back-and-forth loop. The main orchestrator synthesizes their feedback, makes edits, runs tests, and stops when both approve, on stagnation, or after 3 rounds. Use when the user asks to…
blind-spot-pass
Run a pre-build blind spot pass before the agent builds anything. Treat the user's prompt as the map and the real project as the territory: classify gaps across known knowns, known unknowns, unknown knowns, and unknown unknowns (with deps, edge cases, and blast radius under unknown unknowns); ask 5 to 10 high-leverage…
merge-open-prs
Review, verify (Docker by default), and auto-merge open PRs when CI, reviews, and local verification pass. Batch up to 10 PRs per run. Use when the user wants to merge all open PRs, clear the PR queue, or run /merge-open-prs.
deslop
Remove AI-generated code slop and clean up code style.