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/datenoio/internacia-db/openspec-quickstartgit clone --depth 1 https://github.com/datenoio/internacia-dbWhat 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.00518 |
| Opus 5 | $0.00000 | $0.00259 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
openspec-quickstart 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec quickstart for agents
Short guide for schema changes and breaking exports. Full reference: openspec/AGENTS.md.
When to create a proposal
Do propose for: new capabilities, breaking schema/export changes, architecture shifts.
Skip proposal for: bug fixes restoring spec behavior, typos, non-breaking dependency updates, tests for existing behavior.
Checklist
- Run
openspec listandopenspec list --specs— check for conflicts. - Pick a unique verb-led
change-id(e.g.add-field-catalog,update-borders-policy). - Scaffold under
openspec/changes/<change-id>/:proposal.md— why, what, impacttasks.md— implementation checklistdesign.md— only if cross-cutting or ambiguousspecs/<capability>/spec.md— deltas with## ADDED|MODIFIED|REMOVED Requirements
- Every requirement needs at least one
#### Scenario:block. - Run
openspec validate <change-id> --strictand fix all issues. - Do not implement until the proposal is approved.
Scenario format (required)
#### Scenario: Descriptive name
- **WHEN** condition
- **THEN** expected outcome
Use #### Scenario: (four hashes). Bullets or ### Scenario: will fail validation.
MODIFIED requirements pitfall
When modifying an existing requirement, copy the full requirement block from openspec/specs/<capability>/spec.md into the delta and edit it. Partial MODIFIED deltas drop detail at archive time.
Dataset scope
Countries are reference data only. Do not propose socioeconomic profile fields (HDI, GDP, government type, internet penetration).
CLI essentials
openspec list # active changes
openspec list --specs # capabilities
openspec show <id> --json --deltas-only
openspec validate <change-id> --strict
openspec archive <change-id> --yes # after deployment
Workflows
.agent/workflows/openspec-proposal.md— scaffold a change.agent/workflows/openspec-apply.md— implement an approved change.agent/workflows/openspec-archive.md— archive after deployment
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 · 57 lines · 0 tokens per session scan A 138e17dcf264
openspec-quickstart is an agent published in the GitHub repository datenoio/internacia-db (11 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 518 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-30.
Other agents, from other repositories
AUDIT_MANIFEST
Total unimplemented-tagged scenarios: 76 Classified: 76.
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.
architecture-patterns-prompt
You are an architecture and design patterns specialist. Your mission: guide optimal system architecture decisions using proven patterns, modern approaches, and real-world trade-off analysis.
data-engineering-prompt
You are a Data Engineering Specialist who designs and builds robust data pipelines, ensures data quality at scale, and implements both real-time streaming and batch processing architectures. You master modern data stack tools (dbt, Airflow, Spark, Kafka) and guide teams from raw data ingestion to production-ready…
compliance-governance-prompt
You are a Compliance & Governance Specialist who ensures software systems meet regulatory requirements (GDPR, HIPAA, SOC 2, PCI DSS), implements privacy by design, conducts threat modeling, and establishes governance frameworks. You bridge the gap between legal requirements and technical implementation.
monitoring-observability-prompt
You are a monitoring and observability specialist agent. Your mission: instrument systems with the three pillars of observability — logs, metrics, and traces — to ensure production reliability, rapid incident response, and data-driven operational decisions.