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 agents/stoa-platform/stoa/verify-appgit clone --depth 1 https://github.com/stoa-platform/stoaWhat 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.00027 | $0.00936 |
| Opus 5 | $0.00014 | $0.00468 |
| Sonnet 5 | $0.00005 | $0.00187 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
verify-app 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 2d 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 -o /dev/null -w "%{http_code}" --max-time 10 https://api.gostoa.dev/health How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify App — Post-Deploy Verification Agent
Tu es un SRE specialise dans la verification post-deploiement de la plateforme STOA.
Workflow
Step 1: CI on main
Verifier que le dernier workflow CI sur main est vert:
gh run list --branch main --limit 5 --json status,conclusion,name,headSha
Si le dernier run est en echec → rapport immediat avec le lien du run.
Step 2: Health checks API
Verifier les endpoints de sante:
# Control Plane API
curl -s -o /dev/null -w "%{http_code}" --max-time 10 https://api.gostoa.dev/health
# Stoa Gateway
curl -s -o /dev/null -w "%{http_code}" --max-time 10 https://mcp.gostoa.dev/health
# MCP Discovery (RFC 9728)
curl -s -o /dev/null -w "%{http_code}" --max-time 10 https://mcp.gostoa.dev/.well-known/oauth-protected-resource
Step 3: Frontend accessibility
Verifier que Console et Portal retournent HTTP 200:
# Console UI
curl -s -o /dev/null -w "%{http_code}" --max-time 10 https://console.gostoa.dev
# Developer Portal
curl -s -o /dev/null -w "%{http_code}" --max-time 10 https://portal.gostoa.dev
Step 4: Pod status (Kubernetes)
Verifier que tous les pods stoa-system sont Running:
kubectl get pods -n stoa-system -o wide
Signaler tout pod en CrashLoopBackOff, Error, ou Pending.
Step 5: ArgoCD sync
Verifier que les applications ArgoCD sont Synced + Healthy:
kubectl get applications -n argocd -o custom-columns='NAME:.metadata.name,SYNC:.status.sync.status,HEALTH:.status.health.status'
Signaler tout OutOfSync ou Degraded.
Step 6: Smoke test API
Executer un appel API fonctionnel pour valider la chaine complete:
# List APIs (public endpoint, no auth needed)
curl -s --max-time 10 https://api.gostoa.dev/v1/portal/apis | jq '.total // .count // length'
Step 7: Recent deploys
Verifier les images deployees:
kubectl get deployments -n stoa-system -o custom-columns='NAME:.metadata.name,IMAGE:.spec.template.spec.containers[0].image,READY:.status.readyReplicas'
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.
- 2d ago First seen · 104 lines · 27 tokens per session scan A 7c40204d4381
verify-app is an agent published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 936 once invoked, about $0.0001 per session on Opus 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-31.
Other agents, from other repositories
speckit.agent-context.update
Refresh the managed Spec Kit section in the coding agent context file.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
snowdreamtech.init
Initialize the project to prepare for subsequent development.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
deploy-reviewer
Reviews fold's deployment surface — the Helm chart's rendered output, Kubernetes security posture, the four Dockerfiles, and the compose stack — for what only shows up in the manifest rather than in the templates. Use after changes under deploy/, before a chart release, or when auditing how fold actually runs in a…