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 veryfront/veryfront-code --skill deploy-safelygit clone --depth 1 https://github.com/veryfront/veryfront-codeWrote 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/veryfront/veryfront-code/deploy-safely)<a href="https://agentmods.dev/skills/veryfront/veryfront-code/deploy-safely"><img src="https://agentmods.dev/badge/skills/veryfront/veryfront-code/deploy-safely/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/veryfront/veryfront-code/deploy-safely"><img src="https://agentmods.dev/badge/skills/veryfront/veryfront-code/deploy-safely.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.00433 |
| Opus 5.5 | $0.00009 | $0.00173 |
| Sonnet 5.5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
deploy-safely 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
Deploy Safely
Build and test the reviewed Git source, then push it to Veryfront before creating a release and deployment. If verification fails, revert the Git commit and run the normal delivery sequence again.
Steps
-
Build
veryfront build --jsonAbort if
success: false. -
Run tests
veryfront test --jsonAbort if any test fails.
-
Push
veryfront push --branch <branch> --yesAbort if any file fails to upload.
-
Deploy
veryfront deploy --env <environment> --branch <branch> --yes --jsonRecord the project, environment, release, deployment, and commit IDs from the final result record.
-
Verify health (via MCP) Use
vf_get_errorsto check for runtime errors after deploy. Wait 30 seconds, then check again. -
Confirm or rollback
- If no errors: deployment is successful
- If errors are detected, create and push a Git revert:
git revert <bad-commit> git push origin <branch> - Let CI run the normal Push and Deploy steps for the revert. Without CI, repeat steps 3 and 4 manually.
Error Recovery
- Build fails: Check
vf_get_errorsfor compilation errors, fix and retry - Tests fail: Read the JSON output and fix failing tests
- Push fails: Fix the upload failure and rerun Push before Deploy
- Deploy fails: Check environment name, auth token, branch existence
- Post-deploy errors: Revert the failing Git commit, push the revert, then run the normal Push and Deploy sequence
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 · 58 lines · 22 tokens per session scan A 3b730c17a402
deploy-safely is a skill published in the GitHub repository veryfront/veryfront-code (19 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 433 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.