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/samibs/skillfoundry/opsnpx skills add samibs/skillfoundry --skill opsgit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00032 | $0.02085 |
| Opus 5 | $0.00016 | $0.01043 |
| Sonnet 5 | $0.00006 | $0.00417 |
| Haiku 4.5 | $0.00003 | $0.00209 |
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 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.
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 — 229 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.
- 2d ago First seen · 229 lines · 32 tokens per session scan A 5e67102a1dc8
ops is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 2,085 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-30.
Other skills, from other repositories
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…