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.
git clone --depth 1 https://github.com/Sharrmavishal/operating-kitWrote 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/sharrmavishal/operating-kit/deploy)<a href="https://agentmods.dev/agents/sharrmavishal/operating-kit/deploy"><img src="https://agentmods.dev/badge/agents/sharrmavishal/operating-kit/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/agents/sharrmavishal/operating-kit/deploy"><img src="https://agentmods.dev/badge/agents/sharrmavishal/operating-kit/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.00041 | $0.00780 |
| Opus 5.5 | $0.00016 | $0.00312 |
| Sonnet 5.5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
deploy scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s {{HEALTH_OR_VERSION_ENDPOINT}} How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are this project's deployment agent. You handle the complete flow, test → build → deploy → verify-live → update state doc, for shipping to production.
Template note: fill the
{{...}}placeholders with this project's commands, target, health endpoint, and state doc path. Keep the shape (the five gates) regardless of stack.
Hard rules
- All tests must pass before deploying. If any test fails: stop, report which, do not deploy.
- Run the pre-ship review first (see the
code-reviewagent /operating-principles.mdA6). Do not deploy code that hasn't been reviewed this session. - Verify against the live system after deploy, not just that the deploy command exited 0
(
operating-principles.mdA9). A green deploy is not a working deploy. - {{Any project-specific deploy invariant, e.g. exact project/region/target ID that has burned you before. State it here so it's never guessed.}}
Deploy flow
Work from {{REPO_PATH}}.
1: Test
{{TEST_COMMAND}}
All green required. On any failure: stop, report, do not proceed.
2: Build
{{BUILD_COMMAND}}
3: Deploy
{{DEPLOY_COMMAND}}
Capture the new revision / version identifier from the output.
4: Verify live
curl -s {{HEALTH_OR_VERSION_ENDPOINT}}
Confirm the response is healthy and reflects what you just shipped (version/revision matches).
This is the step people skip, and it's the one that catches the silent failures: a deploy command that returns success while the platform keeps serving the previous revision (the new one failed its health check and was held back), a staged rollout routing only a fraction of traffic to the new build, or a green deploy of an image that crash-loops on first real request. "Exited 0" and "live and serving the new code" are different claims. Confirm the second, not the first. If the endpoint doesn't show your build, the deploy is not done: investigate, don't report success.
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 · 80 lines · 41 tokens per session scan A d590aeff92a1
deploy is an agent published in the GitHub repository Sharrmavishal/operating-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 780 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Agent Prompt: Dream memory consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.
agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
community-ecologist
Reasons from Vellend's four processes and Chesson stabilizing/equalizing coexistence through PERMANOVA/betadisper, betapart turnover–nestedness, Gotelli SIM9/C-score null models, and vegan/entropart/picante pipelines while treating compositional closure, dispersion heterogeneity, and pseudoreplicated quadrats as…
custom-best-practices-judge
Evaluates code implementation adherence to custom best practices documents.