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/aoreshkov/oracle-forms-mcp/releasenpx skills add aoreshkov/oracle-forms-mcp --skill releasegit clone --depth 1 https://github.com/aoreshkov/oracle-forms-mcpWrote 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/aoreshkov/oracle-forms-mcp/release)<a href="https://agentmods.dev/skills/aoreshkov/oracle-forms-mcp/release"><img src="https://agentmods.dev/badge/skills/aoreshkov/oracle-forms-mcp/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.00058 | $0.01702 |
| Opus 5 | $0.00029 | $0.00851 |
| Sonnet 5 | $0.00012 | $0.00340 |
| Haiku 4.5 | $0.00006 | $0.00170 |
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 3d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a release
The release workflow (.github/workflows/release.yml) is triggered by a v* tag and its
first step is a hard version-match guard: if the tag doesn't match the version in both
source-of-truth files, the whole release (GitHub release + GHCR image + MCP registry publish)
fails. This skill makes those files agree before the tag is pushed.
1. Determine the new version
Use $ARGUMENTS if given. Otherwise read the current version from gradle.properties
(version=), decide the bump with the user (semver), and confirm. Call the new value
<VERSION> (no v prefix inside files; the git tag is v<VERSION>).
2. Bump the version in BOTH guarded files
The tag guard checks these two exact patterns (keep the formatting identical):
gradle.properties— the lineversion=<VERSION>(guard:^version=<VERSION>$).server.json— the top-level"version": "<VERSION>"(guard:jq .version == <VERSION>). Note: the publish job later rewritesserver.json.versionand.packages[0].identifierfrom the tag, but the guard still requires the committed value to match, so set it here.
There is no third file. The Claude Code plugin manifest
(plugins/oracle-forms/.claude-plugin/plugin.json) has a version too, but it is the plugin's
version, not the project's — bump it only when the plugin's own files change, never as part of a
release. The MCP Implementation version is baked at build time from
project.version into a classpath resource (generateVersionResource in
server/build.gradle.kts → ServerVersion.kt), and the MCPB bundle's manifest version comes from
the same place via the @version@ token in server/mcpb/manifest.template.json — so neither can
drift from gradle.properties. Do not hand-edit a version constant in the Kotlin sources or the
manifest template. The icons[].src URLs in server.json also need no hand-editing: the publish
job re-pins them to the tag (the guard only checks they point at a vX.Y.Z tag, never a branch).
Confirm the two files:
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.
- 3d ago First seen · 117 lines · 58 tokens per session scan A d88db3a19e8f
release is a skill published in the GitHub repository aoreshkov/oracle-forms-mcp (3 stars, last pushed 4d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,702 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-31.
Other skills, from other repositories
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
repo-sweep
Comprehensive pre-production repository audit for preparing repos for public release. Use when the user wants to perform a "final sweep", "production check", "pre-release audit", or prepare a repository to be made public. Audits metadata files across all project types (Fabric mods, Node/npm, Go, Python, etc.) for…
release
Cut an adb-mcp release — review what's landed since the last tag, verify the new tools actually work over a real stdio session, bump the four version files that CI hard-fails on, write the CHANGELOG section that becomes the release notes, replicate the release gate locally, then tag, push, and confirm the GitHub…
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
release-registry
Review the staged PyPI and MCP Registry release workflow for RoastPilot. Use when preparing distribution work and keep current prereqs explicit until release stories land.