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/barrosohub/frontend-stack-blueprint/domaingit clone --depth 1 https://github.com/barrosohub/frontend-stack-blueprintWhat 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.00135 |
| Opus 5 | $0.00000 | $0.00068 |
| Sonnet 5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
domain 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.
What it actually says
Domain docs
This is a single-context repository.
Before exploring
Read these sources when they exist:
CONTEXT.mdat the repository root- ADRs under
docs/adr/
Proceed silently when either source is absent. Create domain documentation only when a term or architectural decision genuinely needs to be recorded.
Vocabulary
Use terms exactly as defined in CONTEXT.md. Do not introduce synonyms for an
existing concept. When a required concept is missing, either reconsider the new
term or record the gap for domain modeling.
ADR conflicts
Surface conflicts with an existing ADR explicitly. Do not silently override a recorded decision.
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 · 25 lines · 0 tokens per session scan A 3d354f0382b1
domain is an agent published in the GitHub repository barrosohub/frontend-stack-blueprint (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 135 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 agents, from other repositories
stack-researcher
Resolves package versions and package identifiers against authoritative sources — the published artifact first, then the registry — before either is written into a blueprint. Use PROACTIVELY whenever a version is about to be pinned, a runtime track is refreshed, an export or option name is in doubt, or the user asks…
designer
Visual designer, UX/UI agent, and Open Design handoff producer.
speckit.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.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
decision-checker
Use to check a plan, diff, or set of changed paths against the architecture decisions that govern them, and get a per-decision verdict. Read-only; never writes a record.
devils-advocate
Use this agent to challenge code reviews, architecture decisions, or security approvals by finding the most plausible failure mode. The Devil's Advocate identifies where systems collapse.