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 agentmods add skills/oneill9/tfl-mcp-server/releasenpx skills add oneill9/tfl-mcp-server --skill releasegit clone --depth 1 https://github.com/oneill9/tfl-mcp-serverWrote 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/oneill9/tfl-mcp-server/release)<a href="https://agentmods.dev/skills/oneill9/tfl-mcp-server/release"><img src="https://agentmods.dev/badge/skills/oneill9/tfl-mcp-server/release.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 | $0.00021 | $0.00491 |
| Opus 5 | $0.00010 | $0.00246 |
| Sonnet 5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
release 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 4d 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.
What it actually says
Prepare a release for version $ARGUMENTS.
Steps
-
Validate the version tag — ensure it starts with
vand follows semver (e.g.v1.0.0). If no argument is provided, ask the user for the version.Before the first npm release, confirm npm trusted publishing for
@oneill9/tfl-mcp-serverauthorizes the GitHub repositoryoneill9/tfl-mcp-server, workflow filerelease.yml, and thenpm publishaction. The release workflow uses GitHub OIDC and intentionally has no long-lived npm token. -
Find the previous tag — run
git tag --sort=-v:refnameto find the most recent existing tag. If there is no previous tag, the changelog covers all commits. -
Generate the changelog — run
git log --oneline <previous-tag>..HEADto get the list of commits since the last release. Group them into a readable changelog with sections like "What's Changed". Include commit messages but exclude merge commits. -
Write RELEASE_NOTES.md — write the changelog to
RELEASE_NOTES.mdin the project root. Format it as:## What's Changed in $ARGUMENTS - Commit message here (short hash) - Another commit message (short hash) ... -
Show the release notes to the user — display the contents of
RELEASE_NOTES.mdand ask the user to confirm or request edits before proceeding. -
Commit the release notes — stage and commit
RELEASE_NOTES.mdwith message:docs: add release notes for $ARGUMENTS -
Create the tag — run
git tag $ARGUMENTS -
Push — run
git push origin main --tagsto push both the commit and the tag. This will trigger the release workflow. -
Confirm — tell the user the tag has been pushed and the GitHub Actions release workflow will create the GitHub release with the committed notes and build artifacts.
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.
- 4d ago First seen · 37 lines · 21 tokens per session scan A 46d0796de079
release is a skill published in the GitHub repository oneill9/tfl-mcp-server (1 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 491 once invoked, about $0.0001 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-31.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…