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 javded-itres/Holix --skill holix-sdd-archivegit clone --depth 1 https://github.com/javded-itres/HolixWrote 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/javded-itres/holix/holix-sdd-archive)<a href="https://agentmods.dev/skills/javded-itres/holix/holix-sdd-archive"><img src="https://agentmods.dev/badge/skills/javded-itres/holix/holix-sdd-archive/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/javded-itres/holix/holix-sdd-archive"><img src="https://agentmods.dev/badge/skills/javded-itres/holix/holix-sdd-archive.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.00028 | $0.00439 |
| Opus 5 | $0.00014 | $0.00219 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
holix-sdd-archive 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 12d 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
When to use
Change is implemented (tasks checked) and user wants to close it / merge requirements into the source of truth.
Workflow
sdd_statuswithchange_id— review remaining open tasks- Confirm with user if any tasks incomplete
sdd_archivewithchange_id- Report
merged_specs, anywarnings(open tasks / not apply_ready), and archive path underopenspec/changes/archive/
Effects
- Delta
## ADDED|MODIFIED|REMOVED Requirementsmerged intoopenspec/specs/<domain>/spec.md - Nested
specs/<domain>/**/spec.mdstill merges into that domain (not a nested folder name as a new domain) - Sections apply in document order (later REMOVED of the same title wins over earlier MODIFIED)
- Duplicate requirement titles in main collapse to one block
- Change directory moved to
openspec/changes/archive/YYYY-MM-DD-<change-id>/ - Open tasks do not block archive; tool returns
warnings— surface them to the user
Merge gotchas
| Issue | Behavior |
|---|---|
| Same title ADDED when already in main | Body replaced (treated as modify) |
| REMOVED then MODIFIED same title | Last section in the delta file wins |
Nested specs/auth/notes/spec.md |
Merges into auth, not domain notes |
| Incomplete tasks | Archive still runs; check warnings |
Do NOT
- Do not archive without user intent for incomplete work
- Do not delete main specs; archive only moves the change folder after merge
- Do not invent main specs by hand after archive — trust
merged_specspaths
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.
- 12d ago First seen · 46 lines · 28 tokens per session scan A 4422745d5748
holix-sdd-archive is a skill published in the GitHub repository javded-itres/Holix (14 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 439 once invoked, about $0.0001 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-30.
Other skills, from other repositories
mnemosyne
Persistent cross-session memory via Mnemosyne — store, recall, and consolidate facts, preferences, and context.
hermes-tweet
Use Xquik in Hermes Agent for public X research, monitoring, thread summaries, creator discovery & approved actions. Not affiliated with X Corp. Use when the user requests X data or a named action. Trigger with "search X", "monitor X", "post tweet", or "X trends".
vrc-monitor-agent
Use for VRChat friend queries (online status, who played with whom, activity timelines, online patterns) and VRChat social actions (boop, invite, join world, friend management, group operations, image uploads) via the vrc-monitor MCP server on port 8799.
openspec-schema-authoring
Create or customize OpenSpec workflow schemas in this repository using openspec schema init and openspec schema fork. Use when the user wants to add, fork, or validate a schema under openspec/schemas/.
review-workflow
A review workflow for GitHub pull requests and issues, including judging whether changes can be merged or an issue can be closed. It requires read-only review, REST API access, and testing changes in practice.
vrchat-social-queries
VRChat social queries: online, companions, patterns, boops.