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.
git clone --depth 1 https://github.com/swesmith/davila7__claude-code-templates.734b8a50Wrote 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/swesmith/davila7__claude-code-templates.734b8a50/services)<a href="https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/services"><img src="https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/services.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.1 | $0.00000 | $0.00605 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
services 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 7d 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.
This is a copy
100% identical to services — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angular Services
Create Angular services for $ARGUMENTS following project conventions.
Task
Create or optimize Angular services based on the requirements:
- Analyze existing services: Check current service patterns, naming conventions, and folder organization
- Examine Angular setup: Review project structure, dependency injection patterns, and TypeScript configuration
- Identify service type: Determine the service category:
- Data services (HTTP API calls, state management)
- Utility services (validation, formatting, helpers)
- Business logic services (calculations, workflows)
- Infrastructure services (logging, authentication, error handling)
- Feature services (component-specific logic)
- Check dependencies: Review existing services and shared modules to avoid duplication
- Implement service: Create service with proper dependency injection and TypeScript types
- Add error handling: Include comprehensive error handling with RxJS operators
- Create tests: Write unit tests with proper mocking following project patterns
- Update module registration: Register service in appropriate Angular modules
Implementation Requirements
- Follow project's Angular architecture and naming conventions (usually .service.ts)
- Use proper dependency injection with @Injectable decorator
- Include comprehensive TypeScript interfaces and types
- Implement proper RxJS patterns (observables, operators, error handling)
- Add proper error handling and logging integration
- Follow single responsibility principle for service design
- Consider service lifecycle and singleton patterns
Service Patterns to Consider
Based on the request:
- HTTP Data Services: API calls with proper error handling and caching
- State Management: Services for sharing data between components
- Authentication: User authentication, token management, guards
- Business Logic: Complex calculations, workflows, validations
- Utility Services: Reusable functions, formatters, validators
- Feature Services: Component-specific logic extraction
- Infrastructure: Logging, monitoring, configuration services
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.
- 7d ago First seen · 62 lines · 0 tokens per session scan A 9102275718b6
services is a command published in the GitHub repository swesmith/davila7__claude-code-templates.734b8a50 (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 605 tokens. A static security scan graded it A with 0 findings. It is 100% identical to services, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
design-form
Design a form with the fewest fields that works, clear labels, and errors that help.
frontend-3d
You are an expert in 3D web development using Three.js, React Three Fiber, WebGL, and WebGPU. You create immersive 3D experiences for the web.
frontend-design
Read and follow the instructions in agents/frontend-design/design-all.md. Also read all referenced files in agents/frontend-design/reference/ as needed for the task.
get-component-source
The full TSX source of a component (append " demo" for its usage example).