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 rijuvashisht/Magneto --skill land-and-deploygit clone --depth 1 https://github.com/rijuvashisht/MagnetoWrote 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/rijuvashisht/magneto/land-and-deploy)<a href="https://agentmods.dev/skills/rijuvashisht/magneto/land-and-deploy"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/land-and-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/rijuvashisht/magneto/land-and-deploy"><img src="https://agentmods.dev/badge/skills/rijuvashisht/magneto/land-and-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.00000 | $0.00476 |
| Opus 5 | $0.00000 | $0.00238 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
land-and-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 11d 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
/land-and-deploy — Merge, Wait for CI, Verify Production
Role: Release Engineer
Inputs: open PR (from /ship)
Outputs: merged PR + deploy verification
Audit actions: land-and-deploy.merged, land-and-deploy.deployed, land-and-deploy.verified
Protocol
Step 1: Merge
gh pr merge <pr-number> --squash --auto
Wait for all required CI checks to pass. If any fail, STOP and report.
Emit audit: land-and-deploy.merged.
Step 2: Wait for deploy
Detect deploy mechanism:
- Vercel: poll deployments API for the commit SHA
- Netlify: poll deploys API
- GitHub Actions deploy: watch the workflow
- Custom: read
.magneto/deploy.jsonfor the check command
Poll every 10s, timeout at 15 minutes.
Emit audit: land-and-deploy.deployed.
Step 3: Verify health
Run production smoke checks:
- HTTP 200 on health endpoint
- Core page renders (via
magneto browse navigate <url>) - No console errors (via
magneto browse eval) - Key feature path still works
If any check fails, flag immediately — don't declare success.
Emit audit: land-and-deploy.verified.
Step 4: Summary
## Deploy Summary
- PR: <url>
- Merged: <ts>
- Deployed: <ts> (<duration>)
- URL: <prod-url>
- Health: ✅
- Rollback command: <vercel rollback sha | netlify rollback | ...>
Configuration
Run magneto setup-deploy (future skill) to configure the deploy command and health checks per project. Until then, use .magneto/deploy.json:
{
"mechanism": "vercel",
"healthUrl": "https://example.com/api/health",
"smokeUrl": "https://example.com/",
"rollback": "vercel rollback <sha>"
}
Trigger Phrases
- "land and deploy"
- "merge and deploy"
- "ship to prod"
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.
- 11d ago First seen · 72 lines · 0 tokens per session scan A 56a683e18d4a
land-and-deploy is a skill published in the GitHub repository rijuvashisht/Magneto (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 476 tokens. 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
publish-npm-package
Configure or troubleshoot npm package publication with GitHub Actions and npm Trusted Publishing. Use this skill for JavaScript or TypeScript packages. Also use it for the npm package in a mixed-language repository. Do not use it for applications or repositories without an npm package. Do not use it for generic CI…
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.