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 synaptiai/synapti-marketplace --skill generating-constrained-specsgit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/generating-constrained-specs)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/generating-constrained-specs"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/generating-constrained-specs/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/synaptiai/synapti-marketplace/generating-constrained-specs"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/generating-constrained-specs.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.00037 | $0.01529 |
| Opus 5 | $0.00018 | $0.00764 |
| Sonnet 5 | $0.00007 | $0.00306 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
generating-constrained-specs 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 10d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Constrained Spec Generation
This skill generates PRD and architecture documents that are constrained by the decision ledger.
Core Principle
No spec section without a DEC- reference.*
Every requirement, every architecture choice, must trace back to an explicit decision. This prevents:
- Ungrounded requirements
- Hidden assumptions
- Scope creep
- Orphaned features
Prerequisites
- Decisions complete (
/ledger-decide) 04-decisions/DECISIONS.yamlexists05-risks/RISKS.yamlexists
Workflow
Use TodoWrite to track these mandatory steps:
Step 1: Load Decisions and Risks
Read:
04-decisions/DECISIONS.yaml- All decisions05-risks/RISKS.yaml- All risks03-synthesis/CROSS-SYNTHESIS.md- Context
Build decision index for quick lookup.
Step 2: Generate PRD
Write 06-prd/PRD.md using template from references/prd-template.md.
Constraint enforcement: Every section heading must include decision reference:
## 2. Target Users (DEC-scope-power-users-first)
Every requirement must cite decisions:
### 2.1 Primary Users
Power users within SMB organizations who manage complex workflows.
(DEC-scope-power-users-first, DEC-scope-smb-segment)
Step 3: Validate PRD Constraint Gate
Check every PRD section:
- Section heading has DEC-* reference
- Requirements cite supporting decisions
- Risks are cross-referenced where relevant
Gate failure: If any section lacks DEC-* reference, cannot proceed.
Step 4: Generate Architecture
Write 07-architecture/ARCHITECTURE.md using template from references/architecture-template.md.
Constraint enforcement:
## 3. Data Model (DEC-tech-postgres-primary, DEC-scope-power-users-first)
### 3.1 Core Entities
Based on power user workflow requirements (DEC-scope-power-users-first),
the data model supports complex nested structures.
What ships with it
3 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.
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.
- 10d ago First seen · 239 lines · 37 tokens per session scan A 6881c6b48380
generating-constrained-specs is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 1,529 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
create-or-update-concepts
Scan and analyze the project codebase to create or update concept files in agents-context/concepts/ (organized by domains/, source/, shared/) and update the README index and Load-When Cheatsheet.
step2-scope-tasks
Break a specification into ordered task groups with explicit context-awareness directives.
step1-write-spec
Gather requirements through structured Q&A, then formalize into a specification document.
create-pr
Creates a GitHub Pull Request on the current branch with a description focused on WHAT changed (not HOW). Uses emojis in the title and description. Use when the user asks to create a PR, open a pull request, or submit changes for review. Triggers on mentions of PR, pull request, merge request, or code review.
step4-archive-spec
Archive a completed spec — moves it to specs-archived and blocks agent access.
plan-product
Define product mission, vision, target users, and technology stack.