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/justdvp/claude-code-templates/composablesgit clone --depth 1 https://github.com/Justdvp/claude-code-templatesWhat 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.00503 |
| Opus 5 | $0.00000 | $0.00251 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
composables 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue Composables
Create Vue composables for $ARGUMENTS following project conventions.
Task
Create or optimize Vue composables based on the requirements:
- Analyze existing composables: Check project for existing composable patterns, naming conventions, and file organization
- Examine Vue setup: Verify Vue 3 Composition API usage and TypeScript configuration
- Identify composable type: Determine the composable category:
- State management (reactive data, computed properties)
- API/HTTP operations (data fetching, mutations)
- DOM interactions (event listeners, element refs)
- Utility functions (validation, formatting, storage)
- Lifecycle management (cleanup, watchers)
- Check dependencies: Review existing composables to avoid duplication
- Implement composable: Create composable with proper TypeScript types and reactivity
- Add lifecycle management: Include proper cleanup with onUnmounted when needed
- Create tests: Write comprehensive unit tests for composable logic
- Add documentation: Include JSDoc comments and usage examples
Implementation Requirements
- Follow project's TypeScript conventions and interfaces
- Use appropriate Vue reactivity APIs (ref, reactive, computed, watch)
- Include proper error handling and loading states
- Add cleanup for side effects (event listeners, timers, subscriptions)
- Make composables reusable and focused on single responsibility
- Consider performance implications (shallow vs deep reactivity)
Common Composable Patterns
Based on the request:
- Data fetching: API calls with loading/error states
- Form handling: Input management, validation, submission
- State management: Local state, persistence, computed values
- DOM utilities: Element refs, event handling, intersection observer
- Storage: localStorage, sessionStorage, IndexedDB
- Authentication: User state, token management, permissions
- UI utilities: Dark mode, responsive breakpoints, modals
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 · 51 lines · 0 tokens per session scan A 0b9e2c215f17
composables is a command published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 503 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-08-31.
Other commands, from other repositories
audit-steps
Audit one or all pipelines against layout, frontmatter, topology, and runtime-safety standards — produces a severity-classified report (SEV-0/1/2/3) with cited evidence.
init-deep
Initiates a repository traversal to create localized PIPELINE-CONTEXT.md hierarchical context files.
migrate-pipeline
Migrate an existing pre-v2 per-tier pipeline (.claude/, .opencode/, .agents/codex/) into the unified data-only .superpipelines/ layout — select legacy pipeline, translate frontmatter to canonical agent defs, stage, delta-audit, gate on human approval, then atomically promote, rewrite the registry, and move the legacy…
delete-step
Delete a step from an existing pipeline — select pipeline, select step, perform gap analysis, optionally rewire, audit the delta, then gate on human approval before any deletion.
new-pipeline
Design and scaffold a new named multi-agent pipeline with git preflight, scope selection, pre-gate audit, and entry-skill generation.
new-step
Add a new step to an existing pipeline — select pipeline, choose insertion point, design component, audit the delta, then gate on human approval.