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 EntityProcess/agentv --skill acme-deploygit clone --depth 1 https://github.com/EntityProcess/agentvWrote 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/entityprocess/agentv/acme-deploy)<a href="https://agentmods.dev/skills/entityprocess/agentv/acme-deploy"><img src="https://agentmods.dev/badge/skills/entityprocess/agentv/acme-deploy/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/entityprocess/agentv/acme-deploy"><img src="https://agentmods.dev/badge/skills/entityprocess/agentv/acme-deploy.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00028 | $0.00354 |
| Opus 5.5 | $0.00011 | $0.00142 |
| Sonnet 5.5 | $0.00006 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
acme-deploy 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 1mo 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
Acme Corp Deployment Procedures
Overview
Internal deployment runbook for Acme Corp services. All deployments follow the Trident release pipeline.
Deployment Commands
Deploy to staging
trident push --env staging --service <service-name> --tag <git-sha>
Promote to production
trident promote --from staging --to prod --service <service-name> --approval-ticket <JIRA-ID>
Production deploys require a JIRA approval ticket (prefix: DEPLOY-).
Rollback
trident rollback --env <env> --service <service-name> --to-version <previous-tag>
Rollbacks auto-notify #ops-alerts in Slack.
Check deployment status
trident status --env <env> --service <service-name>
Service Registry
| Service | Owner Team | Staging URL | Prod URL |
|---|---|---|---|
| payments-api | Platform | payments.staging.acme.internal | payments.acme.internal |
| user-service | Identity | users.staging.acme.internal | users.acme.internal |
| notifications | Engagement | notify.staging.acme.internal | notify.acme.internal |
Rules
- All prod deploys require a DEPLOY- JIRA ticket
- Staging deploys are auto-approved during business hours (9am-5pm PT)
- Rollbacks bypass approval but require post-mortem within 48h
- Deploy freezes are announced in #engineering-announcements
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.
- 1mo ago First seen · 50 lines · 28 tokens per session scan A f9bd48679c5c
acme-deploy is a skill published in the GitHub repository EntityProcess/agentv (15 stars, last pushed 6d ago), licensed MIT. It adds 28 tokens to every session and 354 once invoked, about $0.0001 per session on Opus 5.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.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
changelog-scan
Scan merged PRs and commits since a given reference, extract titles, labels, types, and signals. Produces structured input for release notes drafting.
draft-release-notes
Turn changelog-scan output into polished, categorized release notes draft. Propose only.
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.