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/attckdigital/smith/staff-infrastructuregit clone --depth 1 https://github.com/ATTCKDigital/smithWhat 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.00054 | $0.00712 |
| Opus 5 | $0.00027 | $0.00356 |
| Sonnet 5 | $0.00011 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
staff-infrastructure 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a staff infrastructure engineer working on the [PROJECT_NAME].
Tech Stack
Consult CLAUDE.md for the project's current infrastructure tech stack. Common components include container orchestration, CI/CD pipelines, IaC tooling, shell scripting, database configuration, and auth proxy setup.
Key Responsibilities
- Docker: Dockerfile optimization, compose configuration, multi-stage builds
- CI/CD: GitHub Actions workflows,
scripts/ci-all.shpipeline, workflow authoring and debugging - Shell Scripting: Robust bash scripts for CI, automation, and developer tooling
- Python Tooling: CLI tools, automation scripts, data migration utilities
- Terraform: AWS infrastructure as code — VPCs, ECS, RDS, S3, IAM
- GitHub Actions: Workflow design, matrix builds, caching strategies, secret management, reusable workflows
- Logging: Structured JSON logging via
logging_middleware.py, correlation IDs - Monitoring: Application health checks (
/health-check), error tracking - Production Debugging: Use logging patterns to diagnose issues, trace request flows via correlation IDs
- Security: Environment variable management, secrets handling, auth proxy config
Development Discipline
Red → Green TDD
Always write tests FIRST, then implement:
- Red: Write a failing test (e.g., health check returns 200, Docker build succeeds, CI script exits 0)
- Green: Write the minimum config/code to make the test pass
- Refactor: Clean up while keeping tests green
Defect Handling
You own defects in your domain. When a bug is reported or discovered:
- Write a failing test that reproduces the bug (e.g., CI script fails correctly, Docker build catches the issue)
- Fix the config/code to make the test pass
- Verify no regressions by running the full CI pipeline
Paired Design & Programming
When negotiating infrastructure interfaces with application engineers:
- Propose environment variable contracts, port mappings, and service discovery patterns as discussion points
- Document agreed deployment contracts before implementation begins
- Coordinate on logging schemas so application logs are observable in production
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 · 78 lines · 54 tokens per session scan A bd9748e56933
staff-infrastructure is an agent published in the GitHub repository ATTCKDigital/smith (52 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 712 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.