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 agentmods add skills/paruff/ufawkesai/gitops-simnpx skills add paruff/uFawkesAI --skill gitops-simgit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/gitops-sim)<a href="https://agentmods.dev/skills/paruff/ufawkesai/gitops-sim"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/gitops-sim.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.00488 |
| Opus 5 | $0.00017 | $0.00244 |
| Sonnet 5 | $0.00007 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
gitops-sim 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 3d 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
Skill: Local GitOps Simulation
Load trigger:
"load gitops-sim skill"> DORA: Cap 3 (AI-Accessible Internal Data) Token cost: Low
Purpose
Simulate GitOps updates locally without pushing to remote repos.
Responsibilities
- Clone GitOps repo locally
- Apply OBS updates (image tag, digest)
- Validate manifest correctness
- Validate overlay builds
Inputs
- GitOps repo (local clone)
version.json
Outputs
gitops-sim.json
Simulation Steps
1. Clone/Update GitOps Repo
git clone <gitops-repo> /tmp/local-gitops
cd /tmp/local-gitops
2. Apply OBS Updates
yq -i '.spec.template.spec.containers[0].image = "my-app:v1.2.3" \
overlays/dev/deployment.yaml
3. Validate Overlay
kustomize build overlays/dev | kubectl apply --dry-run=client -f -
4. Commit (Local Only)
git add .
git commit -m "local: simulate OBS update"
Validation Rules
- Overlay builds successfully
- Manifests valid YAML
- Image tag updated correctly
- No syntax errors
Output Format
{
"skill": "gitops-sim",
"status": "success",
"gitops_repo": "/tmp/local-gitops",
"overlay": "overlays/dev",
"updates": [{ "field": "image", "value": "my-app:v1.2.3" }],
"validation": "pass"
}
Success Criteria
- Local GitOps updates match real behavior
- Manifests valid
- No remote push required
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.
- 3d ago First seen · 90 lines · 34 tokens per session scan A 8fd5d294ae8e
gitops-sim is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 11d ago), licensed MIT. It adds 34 tokens to every session and 488 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
infrastructure-overview
Top-level skill for the research template infrastructure layer. Use in Cursor, Claude Code, or similar agents when editing or importing anything under infrastructure/, understanding the two-layer architecture, or wiring build/validation/rendering/publishing. Covers module discovery, import patterns, thin…
template-academic-paper
Template-native manuscript planning, outline, drafting, revision, formatting, citation check, and AI-use disclosure routing. USE WHEN the user asks to write, outline, revise, format, or prepare a paper inside the Research Project Template.
template-code-development
Standards-compliant code for the Research Project Template — infrastructure or project src/, thin orchestrators, type hints, no mocks. USE WHEN implementing an algorithm, utility, analysis method, optimizer, new module in projects//src or infrastructure/, or user says add code following template architecture — even…
template-reproducibility-audit
Deterministic reproducibility audit — fixed seeds, regenerate-from-clean, double-run diff before Zenodo/arXiv/release. USE WHEN outputs drift between runs, "worked on my machine", need regenerate-from-clean proof, or pre-release reproducibility check — even without naming docs/prompts.
template-documentation-creation
Author or refresh AGENTS.md and README.md for template directories — accurate commands, Mermaid where helpful, link generated/activeprojects.md. USE WHEN folder needs AGENTS, README audit, doc contract fix, or signposting after code change — even without documentationcreation prompt.