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 skills add reqvire-org/reqvire --skill sysenggit clone --depth 1 https://github.com/reqvire-org/reqvireWrote 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/skills/reqvire-org/reqvire/syseng)<a href="https://agentmods.dev/skills/reqvire-org/reqvire/syseng"><img src="https://agentmods.dev/badge/skills/reqvire-org/reqvire/syseng/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/reqvire-org/reqvire/syseng"><img src="https://agentmods.dev/badge/skills/reqvire-org/reqvire/syseng.svg" alt="Reviewed on agentmods" width="80" 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.00150 | $0.09311 |
| Opus 5.5 | $0.00060 | $0.03724 |
| Sonnet 5.5 | $0.00030 | $0.01862 |
| Haiku 4.5 | $0.00015 | $0.00931 |
Grade A, and why
reqvire-syseng 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- reqvire-syseng — 92% identical, 52 lines differ
How it starts
The opening of the file, as written. The whole thing — 508 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Engineering and MBSE Skill
You are an expert semantic engineering and MBSE practitioner specializing in Reqvire. You orchestrate Reqvire commands and provide guidance for ontology-driven engineering, capability modeling, requirements, contracts, verification, and AI-native engineering knowledge graphs.
Environment Setup
Use the Reqvire npm runner by default so Codex workflows do not require a separate binary install.
Default command form:
npx -y "${REQVIRE_NPX_PACKAGE:-@reqvire-org/reqvire@latest}" --workspace "$PWD" <command>
Workspace policy:
- Run commands from the intended effective workspace root, or pass that root with
--workspace. - The effective workspace root must contain at least one eligible Git worktree; otherwise there is no local SOI model-processing scope.
- Reqvire parses and reports only files and artifacts under the effective workspace root that are inside eligible Git worktrees. Non-Git workspace folders are ignored.
- Git worktree roots, branches, remotes, and commits are source-control metadata. They do not redefine Reqvire identifier roots; identifiers and paths stay workspace-root-relative.
To check:
npx -y "${REQVIRE_NPX_PACKAGE:-@reqvire-org/reqvire@latest}" --workspace "$PWD" --version
Version policy:
- Use
@reqvire-org/reqvire@latestby default for assistant workflows. - Pin by setting
REQVIRE_NPX_PACKAGE, for exampleexport REQVIRE_NPX_PACKAGE=@reqvire-org/[email protected]. - Use a locally installed
reqvirebinary only when the user explicitly needs offline or non-npm execution.
Element Types
| Category | Type | Purpose |
|---|---|---|
| Capabilities | capability |
Coherent operational, product, business, regulatory, or system ability that bridges ontology, requirements, and verification |
| Requirements | requirement |
Implementable system obligations (functional, performance, interface, compliance) |
| Ontology | ontology |
First-class OWL/Turtle vocabulary and semantic model terms reusable by capabilities and requirements |
semantic-contract |
Reusable SHACL shape profile that uses ontology and constrains requirements | |
semantic-query |
Managed SPARQL artifact with explicit ontology context, deterministic export, and downstream execution | |
| Concepts | concept-scheme |
Native SKOS thesaurus or concept-scheme root that owns concept_base and concept_prefix |
concept |
Native curated SKOS concept generated from Markdown body text, labels, examples, and concept relations | |
| Contracts | source |
External need, regulation, policy, or source material owned by a requirement |
specification |
Detailed definitions refining a requirement | |
constraint |
Limits and boundaries on system behavior | |
behavior |
How the system behaves in specific conditions | |
state |
Lifecycle states, state machines, transitions, and state-dependent contracts | |
input-output |
Payloads, messages, documents, schemas, fixtures, and data contracts | |
| Verification planning | verification-objective |
Verification objective or grouping node; may derive from verification-family elements but does not verify requirements/capabilities and cannot use satisfiedBy |
| Verifications | test-verification |
Automated/manual testing (evidence-backed; requires satisfiedBy) |
formal-proof-verification |
Formal proof, model checking, theorem proving, generated fixtures, or proof reports (evidence-backed; requires satisfiedBy) | |
analysis-verification |
Review, calculation, simulation | |
inspection-verification |
Visual examination, audit | |
demonstration-verification |
Showing capability works |
What ships with it
20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- reference/AddCapability.md 24 KB
- reference/AddRequirement.md 5.5 KB
- reference/AddVerification.md 8.7 KB
- reference/CapabilitySemanticContractRefactor.md 14 KB
- reference/Collect.md 6.7 KB
- reference/ConsolidateRequirements.md 14 KB
- reference/Containment.md 5.3 KB
- reference/ContainmentStructureRefactor.md 11 KB
- reference/CreatingTasks.md 16 KB
- reference/DesignDocOwnership.md 2.5 KB
- reference/explore.md 8.8 KB
- reference/Link.md 5.9 KB
- reference/Move.md 9.5 KB
- reference/Remove.md 2.7 KB
- reference/RenameElement.md 2.5 KB
- reference/Setup.md 3.7 KB
- reference/SpecificationLanguageCleanup.md 2.8 KB
- reference/SpecificationsExtractionLogic.md 14 KB
- reference/SubmodelRefactor.md 7.1 KB
- reference/VerificationAlignment.md 1.2 KB
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.
- 11d ago Changed · +35 lines 93c218ea8eee
- 1mo ago Changed · -1 lines 2a4440f7265b
- 1mo ago First seen · 474 lines · 150 tokens per session scan A 2120469a30c1
reqvire-syseng is a skill published in the GitHub repository reqvire-org/reqvire (27 stars, last pushed yesterday), licensed Apache-2.0. It adds 150 tokens to every session and 9,311 once invoked, about $0.0006 per session on Opus 5.5. 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-09-01.
Other skills, from other repositories
debug
Systematic debugging with persistent state across context resets.
thread
Manage persistent context threads for cross-session work.
research-phase
Research how to implement a phase (standalone - usually use /gsd:plan-phase instead).
add-backlog
Add an idea to the backlog parking lot (999.x numbering).
workstreams
Manage parallel workstreams — list, create, switch, status, progress, complete, and resume.
set-profile
Switch model profile for GSD agents (quality/balanced/budget/inherit).