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 digital-stoic-org/agent-skills --skill openspec-reflectgit clone --depth 1 https://github.com/digital-stoic-org/agent-skillsWrote 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/digital-stoic-org/agent-skills/openspec-reflect)<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/openspec-reflect"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/openspec-reflect/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/digital-stoic-org/agent-skills/openspec-reflect"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/openspec-reflect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Excessive Agency · line 75 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00035 | $0.01191 |
| Opus 5.5 | $0.00014 | $0.00476 |
| Sonnet 5.5 | $0.00007 | $0.00238 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
openspec-reflect 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 1mo 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Reflect
Pre-gate self-check skill. Verifies acceptance criteria, detects scope drift, and ensures philosophy alignment before human review.
Workflow: Check → Assess → Report
flowchart LR
A["Read context"] --> B["Check criteria"]
B --> C["Detect drift"]
C --> D["Check philosophy"]
D --> E["Self-assess"]
E --> F["Generate report"]
classDef action fill:#E1BEE7,stroke:#7B1FA2,color:#000
class A,B,C,D,E,F action
Critical: Run before human gates. Catches drift BEFORE human reviews.
Commands
reflect
Run comprehensive pre-gate self-check.
Input: $ARGUMENTS = change-id
Workflow:
-
Load context:
- Read
openspec/changes/{change-id}/proposal.mdfor acceptance criteria - Read
openspec/changes/{change-id}/tasks.mdfor progress - Read
openspec/changes/{change-id}/test.mdfor test strategy (if exists) - Read
openspec/changes/{change-id}/specs/*.mdfor requirements - Read
openspec/project.mdfor Execution Philosophy
- Read
-
Pre-gate check (scale/maintenance mode only):
- Check if
test.mdexists - If missing in scale/maintenance mode: flag ⚠️ MISSING_TEST_MD deviation
- In garage mode: test.md optional (note if missing, don't block)
- Check if
-
Check acceptance criteria:
- Extract criteria from proposal.md (Success Criteria section)
- For each criterion: verify met/unmet/partial
- Record evidence for each status
-
Detect scope drift:
- Extract "Affected files" from proposal.md
- Run
git statusandgit diff --statto find actual changes - Calculate deviation percentage:
(actual - proposed) / proposed * 100 - Flag if >20% deviation
-
Check philosophy alignment:
- Read
modefrom Execution Philosophy - Review implementation for anti-patterns of current mode
- Flag any violations
- Read
-
Self-assessment:
- Answer: "Am I solving the right problem?"
- Evaluate: Is work aligned with proposal's Problem statement?
What ships with it
1 file 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.
- 1mo ago First seen · 147 lines · 35 tokens per session scan A f4136042cf73
openspec-reflect is a skill published in the GitHub repository digital-stoic-org/agent-skills (20 stars, last pushed 12d ago), licensed MIT. It adds 35 tokens to every session and 1,191 once invoked, about $0.0001 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-04.
Other skills, from other repositories
tech-debt
Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…