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/KaelSensei/MagicAIBuilderWrote 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/commands/kaelsensei/magicaibuilder/devops)<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/devops"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/devops/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/commands/kaelsensei/magicaibuilder/devops"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/devops.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.02295 |
| Opus 5.5 | $0.00000 | $0.00918 |
| Sonnet 5.5 | $0.00000 | $0.00459 |
| Haiku 4.5 | $0.00000 | $0.00230 |
Grade A, and why
devops 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.
How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Command – Infrastructure & CI/CD Workflow
When /devops <task description> is invoked, immediately execute the following steps to create, configure, or manage DevOps infrastructure, CI/CD pipelines, and deployment configurations.
Step 1: Load Project Context & Follow All Rules
- Assume the project root as the working directory
- Load and strictly follow ALL Cursor rules from
.cursor/rules/*.mdc:security.mdc- Security requirements (especially for secrets, credentials, and deployment)technical-stack.mdc- React Native/Android build patternsdocumentation.mdc- Documentation update requirementsversion-management.mdc- Git commit/push workflow
- Read relevant documentation:
README.mdPROGRESS.md- Any existing DevOps documentation (e.g.,
PLAY_STORE_DEPLOYMENT.md) - Architecture and deployment documents
- Identify the current Git branch and assume it is a feature branch, not
main - Check for attachments (diagrams, existing configs, requirements):
- Analyze any visual references or existing configurations
- Extract deployment requirements, environment specifications
- Use attachments to clarify infrastructure needs
- If attachments conflict with description, ask for clarification
Step 2: Understand the DevOps Task
- Parse the task description provided after
/devops - Incorporate context from any attached files or diagrams:
- Existing CI/CD configurations
- Infrastructure diagrams
- Deployment workflows
- Environment specifications
- Clearly define:
- What DevOps infrastructure needs to be created or modified
- Which tools/services are involved (GitHub Actions, Kubernetes, Docker, etc.)
- What the expected deployment workflow is
- What environments are needed (dev, staging, production)
- Identify impacted areas:
- CI/CD pipeline configurations (
.github/workflows/) - Kubernetes manifests (
k8s/orkubernetes/) - Docker configurations (
Dockerfile,docker-compose.yml) - Build scripts (
package.json,scripts/) - Environment configuration files (
.env.example,.env.production) - Deployment documentation
- CI/CD pipeline configurations (
- If requirements or scope are unclear (even with attachments), stop and ask before proceeding
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 · 299 lines · 0 tokens per session scan A 41cc327e141c
devops is a command published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,295 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 commands, from other repositories
add-endpoint
Scaffold a new API endpoint with full layering.
review
Review code changes against project conventions.
fix-issue
Investigate and fix an issue.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.