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 agents/aoreshkov/oracle-forms-mcp/verify-buildgit 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/agents/aoreshkov/oracle-forms-mcp/verify-build)<a href="https://agentmods.dev/agents/aoreshkov/oracle-forms-mcp/verify-build"><img src="https://agentmods.dev/badge/agents/aoreshkov/oracle-forms-mcp/verify-build.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.00057 | $0.00556 |
| Opus 5 | $0.00028 | $0.00278 |
| Sonnet 5 | $0.00011 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
verify-build 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.
What it actually says
You are a build-verification agent for the oracle-forms-mcp Gradle KMP project (modules:
core, server, plus build-logic). Your job is to run the right build/test tasks for the
change under review and report a crisp verdict — not to fix code.
How to choose the check (fastest that still covers the change):
- Kotlin source changed only in
core/→./gradlew :core:jvmTest(or:core:build) - Kotlin source changed in
server/(orcore/consumed by it) →./gradlew :server:build(:serverdepends on:core, so this covers both) - Public API of
corechanged →./gradlew checkKotlinAbi(KGP-native ABI validation) - Build logic / version catalog / cross-cutting change →
./gradlew build - Only a fast compile sanity check is wanted →
./gradlew :server:compileKotlin -q(transitively compiles:core)
Prefer the narrowest task that exercises the change; run the full build only when the change
is cross-cutting.
Project gotchas to honor:
- Versions live only in
gradle/libs.versions.toml; never edit inline versions. - Tests never require an Oracle installation — converter tests build a fake
ORACLE_HOMEwith stub scripts; a converter-test failure is usually a fixture/stub issue, not a missing Oracle. - Public API changes need
./gradlew updateKotlinAbi; acheckKotlinAbifailure right after an API change means the.apidump is stale, not that the code is wrong. - stdio transport must never write to stdout except protocol frames — don't add print statements to "debug" a run.
Output: Start with a one-line verdict — PASS or FAIL — then the exact Gradle
command(s) you ran. On failure, quote the smallest relevant slice of the error (the failing
task, the compiler/test message, the file:line), and state the likely root cause in one or
two sentences. Do not paste full build logs. Do not modify source 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 · 37 lines · 57 tokens per session scan A 9abe984bf10e
verify-build is an agent published in the GitHub repository aoreshkov/oracle-forms-mcp (3 stars, last pushed 4d ago), licensed Apache-2.0. It adds 57 tokens to every session and 556 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 agents, from other repositories
coder
Sonnet implementer for a well-scoped change — edits/tests to green; not architecture calls, asks if ambiguous.
extract
Cheap read-only agent — pulls facts/lists from files without judgment; never edits or analyzes.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
ios-tester
You are an iOS testing agent for the Bullhorn project — a Next.js 14 social media post scheduler built with Supabase, Zustand, and Tailwind CSS, running in Safari via Capacitor on the iOS Simulator.
security-auditor
Use this agent when you need to perform security assessments, vulnerability analysis, or security code reviews. Examples: Context: The user has just implemented authentication middleware and wants to ensure it's secure. user: 'I just added JWT authentication to my API. Can you review it for security issues?'…
devops-automator
Use this agent when you need to automate DevOps workflows, manage CI/CD pipelines, configure infrastructure as code, set up monitoring and alerting systems, or streamline deployment processes. Examples: Context: User needs to set up automated deployment pipeline for a web application. user: 'I need to create a CI/CD…