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 FoloToy/ai-passport --skill experience-prgit clone --depth 1 https://github.com/FoloToy/ai-passportWrote 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/folotoy/ai-passport/experience-pr)<a href="https://agentmods.dev/skills/folotoy/ai-passport/experience-pr"><img src="https://agentmods.dev/badge/skills/folotoy/ai-passport/experience-pr/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/folotoy/ai-passport/experience-pr"><img src="https://agentmods.dev/badge/skills/folotoy/ai-passport/experience-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 121 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00031 | $0.01797 |
| Opus 5 | $0.00015 | $0.00898 |
| Sonnet 5 | $0.00006 | $0.00359 |
| Haiku 4.5 | $0.00003 | $0.00180 |
Grade A, and why
experience-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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Collect Development Experience and Submit a PR
This skill captures the reusable, durable learnings from a firmware release and
proposes them as a documentation pull request to the upstream
FoloToy/ai-passport project. It runs only after a release and only when the
developer explicitly asks to collect experience.
Safety and consent gate (run first)
Do not collect, draft, or submit anything until every gate below is satisfied. These gates are the highest-priority constraints.
- Confirm consent up front. This work touches project-private content. Ask the developer to confirm they agree to start the post-release follow-up before collecting anything. If they decline, stop immediately.
- Check GitHub access. Confirm a GitHub channel is available before
submitting. Try the configured channels in order and use the first one that
works: GitHub MCP (when present and authenticated), a GitHub skill (for
example the installed
cindy-githubcapability), then theghCLI (gh auth status). If none is available, generate the complete change content for the developer to paste manually and stop; never submit on their behalf. - Never modify or commit on the current branch. The release experience is
usually derived from the current working branch, but the change must not
be committed on the developer's current branch. Base the work on the latest
upstream
mainfor a clean baseline, create a dedicated branch or worktree, push it to the developer's fork (origin), and open the PR from that fork branch against the upstreamFoloToy/ai-passport. Leave the current checkout untouched. - Never submit before review. Draft everything first, show it to the developer, and wait for explicit approval. Do not commit, push, or open a PR until the developer has reviewed and authorized it. Opening a PR also requires separate confirmation.
- No credentials or private data. Never include credentials, device QR
secrets, private device links, personal data, or unsanitized logs. Run
python3 tools/check_repo.pybefore committing anything.
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.
- 6d ago Changed bc1194c4a2be
- 10d ago First seen · 169 lines · 31 tokens per session scan A e843d99edfef
experience-pr is a skill published in the GitHub repository FoloToy/ai-passport (279 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,797 once invoked, about $0.0002 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.