Borrowing it
Nothing to install: this file belongs to aiblueprinthq/ai-blueprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aiblueprinthq/ai-blueprint/main/.agents/skills/try/SKILL.mdgit clone --depth 1 https://github.com/aiblueprinthq/ai-blueprintWrote 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/aiblueprinthq/ai-blueprint/try)<a href="https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/try"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/try/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/aiblueprinthq/ai-blueprint/try"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/try.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.00054 | $0.01202 |
| Opus 5 | $0.00027 | $0.00601 |
| Sonnet 5 | $0.00011 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
try 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
try - manual review guide
Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.
Where this sits in the workflow:
/implement or /complete -> [try] -> human review
(work exists) (manual (where to go,
path) what to click)
/check proves behavior from the agent side. /try gives the user a practical
manual walkthrough: start this command, open this route, click these controls,
expect this result, and watch for these failure signs.
It is always read-only. It does not edit files, install dependencies, commit, merge, push, or run destructive commands.
The quality-gate config controls when another workflow generates this guide
automatically. An explicit /try or $try request always runs. A generated guide
never counts as evidence that the user performed the walkthrough.
Input
Optional scope:
- no argument: use the active feature, fix, or rollback in
blueprint/context/current-feature.md latest: use the most recent archive underblueprint/history/features/,blueprint/history/fixes/, orblueprint/history/rollbacks/- a step name or number: focus the guide on that current-feature step
- a path, route, or command: include it as the main thing to try
If there is no active feature and no useful archive, ask what change the user wants to try instead of guessing.
Step 1 - find the work to explain
Read:
AGENTS.mdblueprint/config.jsonblueprint/context/current-feature.mdblueprint/context/project-overview.mdblueprint/context/coding-standards.mdblueprint/build-plan.md- latest files under
blueprint/history/features/,blueprint/history/fixes/, andblueprint/history/rollbacks/, if the current feature is reset - git branch and working tree status
Prefer the active spec. If current-feature.md is the reset stub, use the most
recent archived feature, fix, or rollback by filename or modification time and
say that is what you used.
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 Changed · +2 lines · -66 tokens per session afc618a5970e
- 10d ago First seen · 126 lines · 120 tokens per session scan A 8f5c15313e16
try is a skill published in the GitHub repository aiblueprinthq/ai-blueprint (384 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 1,202 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.