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/lukasrepublic/agentic-foundry/deploy-statusnpx skills add lukasrepublic/agentic-foundry --skill deploy-statusgit clone --depth 1 https://github.com/lukasrepublic/agentic-foundryWrote 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/lukasrepublic/agentic-foundry/deploy-status)<a href="https://agentmods.dev/skills/lukasrepublic/agentic-foundry/deploy-status"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/deploy-status.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.00100 | $0.00982 |
| Opus 5 | $0.00050 | $0.00491 |
| Sonnet 5 | $0.00020 | $0.00196 |
| Haiku 4.5 | $0.00010 | $0.00098 |
Grade A, and why
deploy-status 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/foundry:deploy-status
Observe-only. Deploy = CD (ArgoCD App-of-Apps, GitOps from the infra repo); Foundry does NOT own the deploy action — it observes. Production deploy is operator-gated under BOTH modes; there is no autonomous prod-deploy.
When to trigger
- "deploy status", "/foundry:deploy-status", "what's synced/healthy in
<env>?". - NEVER to initiate a deploy (that's the operator + CD).
Procedure
- Cross-check deployed-artifact identity (STALE/NOT-ROLLED). Before trusting
sync+health, confirm the merged commit actually rolled. A
workflow_run-gated CD pipeline silently skips when its upstream CI false-reds: the merged commit never builds, gitops is never written back, the old image keeps running — and ArgoCD then reads "Synced + Healthy" against the stale image. Run the identity check:
It compares each target's deployed gitopspython3 "${CLAUDE_PLUGIN_ROOT}/scripts/foundry-deploy-status.py" \ --config "$CLAUDE_PROJECT_DIR/.foundry/deploy-targets.yaml"image.tagagainst the expected merged-commit identity (the target repo'smainHEAD / its build-provenance SHA) and reports:ROLLED— deployed identity == expected, upstream CIsuccess.STALE/NOT-ROLLED— identity mismatch or the expected commit's CI was notsuccess(the gated build skipped). This is reported independently of sync/health, so a Synced+Healthy stale image can never read GREEN. When the cause is the skipped build it is namedupstream-ci-not-success, distinct from a bare identity drift. The expected-SHA→gitops-path mapping is adopter-config (.foundry/deploy-targets.yaml, shape indeploy-targets.example.yaml); no product specifics ship in the plugin.
- Observe ArgoCD sync + health for the target env's apps (read-only):
argocd app list/argocd app get <app>(or thegh/kubectlread equivalents). Report per-app sync status (Synced/OutOfSync) + health (Healthy/Degraded/Progressing). - Correlate a merged atom to its rollout (the marker's
model_pin/built_ataid incident forensics) — but do NOT mutate cluster state. - Escalate a
STALE/NOT-ROLLED, Degraded, or OutOfSync prod app by notifying the operator; resolution is forward-fix (re-trigger the build / merge) or/foundry:revert— never a silent cluster edit.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 62 lines · 100 tokens per session scan A 8c5487c2cfbd
deploy-status is a skill published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 982 once invoked, about $0.0005 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
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…