Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bjcoombs/ai-native-toolkit/plugin install ai-native-toolkitWrote 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/bjcoombs/ai-native-toolkit/assess-pr)<a href="https://agentmods.dev/skills/bjcoombs/ai-native-toolkit/assess-pr"><img src="https://agentmods.dev/badge/skills/bjcoombs/ai-native-toolkit/assess-pr.svg" alt="Measured on agentmods" 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.00067 | $0.06695 |
| Opus 5 | $0.00034 | $0.03348 |
| Sonnet 5 | $0.00013 | $0.01339 |
| Haiku 4.5 | $0.00007 | $0.00670 |
Grade A, and why
assess-pr 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 6d 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assess PR and Issues
The end-of-run half of /assess. The report (.assess/assess-report.md), the complexity heatmap, and the doc graph are written. This step runs the optional end-of-run offers - in order - then closes the loop:
- Open a PR with the report (Step 5).
- Track the Top 3 Actions in the user's issue tracker (Step 6).
- Freeze the assessment into a CI gate (Step 6.5).
- Tool feedback (Step 7) - surface anomalies and offer to file feedback.
- Uninstall
/assess(Step 8) - the escape hatch: remove everything this run wrote.
Each offer is independent (uninstall excepted - it's mutually exclusive with the write-back offers): a user can accept any subset. The step references back into the written assess-report.md artifact (notably the Top 3 Actions table's Issue column), not into the scoring prose, so it stays decoupled from how the report was produced.
Phase 2: ask once, batched (and the non-interactive contract)
These are the write-back phase of the consent lifecycle (Phase 2; Phase 1 was the tool installs, Phase 3 the mutation pass - see the assess SKILL.md). Do not serialise them into back-to-back modals. Present them as one batched, multi-select AskUserQuestion: "Now that the report is written, which of these should I do?" with the options (open a PR, track the Top 3 Actions, freeze a CI gate, file feedback, and - the mutually-exclusive escape hatch - uninstall /assess from this repo), pre-filtered by feasibility:
- Drop the PR option when the push-capability / remote check below (Step 5) shows no direct or fork PR is possible; on a read-only target, offer the fork variant instead.
- Drop the CI gate option when the workflow could never run (no GitHub remote).
- Keep issue tracking and feedback always (feedback needs no repo write).
- Uninstall (Step 8) always appears: it removes what this run wrote. It doesn't compose with the write-back offers (no point opening a PR and deleting the report), so treat selecting it as "skip the others and clean up".
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.
- 6d ago First seen · 344 lines · 67 tokens per session scan A 1b6c42f0cb86
assess-pr is a skill published in the GitHub repository bjcoombs/ai-native-toolkit (30 stars, last pushed yesterday), licensed Apache-2.0. It adds 67 tokens to every session and 6,695 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-30.
Other skills, from other repositories
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.