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 skills add tranhieutt/software_development_department --skill team-backendgit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/team-backend)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/team-backend"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-backend/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/team-backend"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-backend.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00053 | $0.00543 |
| Opus 5 | $0.00026 | $0.00271 |
| Sonnet 5 | $0.00011 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
team-backend 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 8d 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.
What it actually says
When this skill is invoked, orchestrate the backend team through a structured delivery pipeline.
Decision Points: At each phase, use AskUserQuestion to get user approval before proceeding.
Team Composition
- technical-director — Architecture review and approval
- backend-developer — API and service implementation
- data-engineer — Schema design and migrations
- security-engineer — Security review
Pipeline
Phase 1: Architecture Design
Delegate to technical-director:
- Review the system requirements
- Propose architecture: service boundaries, data flows, technology choices
- Identify risks and cross-cutting concerns
- Output: Architecture proposal for approval
Phase 2: Schema Design
Delegate to data-engineer:
- Design database schema based on approved architecture
- Write migration scripts (up and down)
- Define indexes and constraints
- Output: Schema design doc + migration files for review
Phase 3: API Contract Design
Delegate to backend-developer:
- Define REST/GraphQL endpoint contracts
- Specify request/response schemas and error codes
- Define authentication requirements per endpoint
- Output: API contract for frontend team to build against
Phase 4: Implementation
Delegate to backend-developer:
- Implement approved endpoints
- Apply approved schema migrations
- Write unit and integration tests
- Output: Implemented and tested backend
Phase 5: Security Review (parallel with implementation where possible)
Delegate to security-engineer:
- Review auth and authorization logic
- Check for injection vulnerabilities, insecure data exposure
- Validate input sanitization
- Output: Security review report
Phase 6: Integration
- Address security findings
- Confirm API is ready for frontend integration
- Run
/db-reviewand/api-designchecks
Output
Summary covering: architecture decision, schema status, API contract, test coverage, and security review result.
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.
- 8d ago First seen · 66 lines · 53 tokens per session scan A abb2a8dda9ce
team-backend is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 543 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-09-03.
Other skills, from other repositories
openloomi-api
OpenLoomi ships a local-first HTTP API served from the desktop app (port 3414, fallback 3515). All auth, Memory, AI, RAG, Loop, and Audit data live in a local SQLite database — your data stays on your machine and the OpenLoomi app is the source of truth. The only externally-routed auth path is the Composio OAuth…
phoenix-contexts
Phoenix context design — creating/splitting contexts, Scope (1.8+), Ecto.Multi, PubSub, routers, plugs, controllers. Use when editing contexts, routers, or designing boundaries.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
511-frameworks-micronaut-jdbc
Use when you need programmatic JDBC in Micronaut — pooled DataSource, parameterized SQL, io.micronaut.transaction.annotation.Transactional, batching, and domain exception translation. This should trigger for requests such as Review JDBC or SQL data access in a Micronaut project; Improve transactions and parameter…
512-frameworks-micronaut-data
Use when you need data access with Micronaut Data — @MappedEntity, CrudRepository/PageableRepository, @Query with parameters, @Transactional services, projections, @Version, and @MicronautTest with TestPropertyProvider and Testcontainers. For raw java.sql access without generated repositories, use…
event-sourcing-architect
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trails, or temporal queries.