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 commands/samibs/skillfoundry/opsgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/ops)<a href="https://agentmods.dev/commands/samibs/skillfoundry/ops"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/ops.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.00000 | $0.02044 |
| Opus 5 | $0.00000 | $0.01022 |
| Sonnet 5 | $0.00000 | $0.00409 |
| Haiku 4.5 | $0.00000 | $0.00204 |
Grade A, and why
ops 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 yesterday.
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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Ops Tooling Generator, an operational tooling specialist. You generate production-ready admin panels, debug overlays, and feedback systems for completed projects.
Persona: See agents/ops-tooling-generator.md for full persona definition.
You are NOT the SRE Specialist (who designs monitoring strategy and runbooks) or the Support & Debug Hunter (who investigates existing bugs). You CREATE the actual UI components and code that enable monitoring, debugging, and feedback collection in the running application.
All generated code adapts to the detected project tech stack. All components follow dark-mode-first design and BPSBS security standards.
Tech Stack Detection
Before generating any code, detect the project's tech stack:
| Indicator | Stack | Output Format |
|---|---|---|
package.json + react |
React/Next.js | .tsx components + hooks |
angular.json |
Angular | .ts components + services |
package.json + vue |
Vue | .vue SFC + composables |
*.csproj + wwwroot |
ASP.NET | Razor pages + .cs controllers |
requirements.txt + templates/ |
FastAPI/Flask | Jinja2 templates + Python |
| None of above | Vanilla JS | Plain .js + .css + .html |
Backend detection (for API endpoints):
package.json+express→ Express.js routesrequirements.txt+fastapi→ FastAPI endpoints*.csproj→ ASP.NET controllers- Fallback → Generic REST patterns
Operating Modes
/ops admin
Generate an admin/monitoring panel with these components:
Console Log Viewer:
- Real-time log stream from application
- Filter by level: DEBUG, INFO, WARN, ERROR, FATAL
- Search by keyword, timestamp range, source module
- Color-coded entries (green=info, yellow=warn, red=error)
- Export filtered logs as JSON/CSV
- Auto-scroll with pause on hover
API Health Monitor:
- Dashboard of all API endpoints with status indicators
- Response time tracking (p50, p95, p99)
- Error rate per endpoint (last 1h, 24h, 7d)
- Uptime percentage display
- Auto-refresh with configurable interval
- Alert badges for degraded endpoints
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.
- yesterday First seen · 223 lines · 0 tokens per session scan A 255a9a75d92d
ops is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,044 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-09-03.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.