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/justifi-tech/web-component-library/setupgit clone --depth 1 https://github.com/justifi-tech/web-component-libraryWhat 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.00581 |
| Opus 5 | $0.00000 | $0.00291 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
setup 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 yesterday.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are helping set up a new specd project. The framework files have already been installed via specd init. Your job is to customize them for this specific project.
Study the codebase first — read existing code, build files, configs, package manifests, Dockerfiles, Makefiles, CI configs, and anything that reveals the tech stack, conventions, and project structure.
Then work through each step interactively with the human. Ask questions, propose answers based on what you found, and get confirmation before writing.
Step 1: AGENTS.md — Build & Test
Read AGENTS.md. The Build & Test section has a placeholder comment.
Based on what you found in the codebase, propose concrete build and test commands. Examples:
make check,cargo test,go test ./...,npm test,pytest- Linters, formatters, type checkers
- Integration test commands if they exist
Ask the human to confirm or adjust, then update the section.
Step 2: AGENTS.md — Conventions
The Conventions section has a placeholder comment.
Based on the codebase, propose language-specific conventions:
- Language and version
- Naming conventions (casing, prefixes)
- Import ordering
- Error handling patterns
- Any patterns you see repeated in the existing code
Ask the human to confirm or adjust, then update the section.
Step 3: .claude/commands/specd/implement.md — Validation
Read .claude/commands/specd/implement.md. The validation section has a placeholder comment.
Propose concrete validation steps that match this project's tooling:
- Test command(s) to run
- Lint/format checks
- Type checking
- Any other pre-commit validation
Ask the human to confirm or adjust, then update the section.
Step 4: First spec
Ask the human what they want to build first. Help them write a spec following the format in specs/example-spec.md.
- Start at Draft status
- Fill in Overview, Scope, Dependencies, and as much of the Specification section as they're ready for
- Add it to the phase table in
specs/README.md
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.
- yesterday First seen · 64 lines · 0 tokens per session scan A f16c7e059084
setup is a command published in the GitHub repository justifi-tech/web-component-library (5 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 581 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.