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 jumppad-labs/spektacular --skill spek-knowledgegit clone --depth 1 https://github.com/jumppad-labs/spektacularWrote 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/jumppad-labs/spektacular/spek-knowledge)<a href="https://agentmods.dev/skills/jumppad-labs/spektacular/spek-knowledge"><img src="https://agentmods.dev/badge/skills/jumppad-labs/spektacular/spek-knowledge/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/jumppad-labs/spektacular/spek-knowledge"><img src="https://agentmods.dev/badge/skills/jumppad-labs/spektacular/spek-knowledge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
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 →
- high Tool Misuse · line 61 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 76 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 25 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.00017 | $0.03993 |
| Opus 5.5 | $0.00007 | $0.01597 |
| Sonnet 5.5 | $0.00003 | $0.00799 |
| Haiku 4.5 | $0.00002 | $0.00399 |
Grade A, and why
spek-knowledge 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version check first. Before running any other command, run
go run . version check.
- On
status: "match", continue with the skill and produce no version-related output.- On
"mismatch","missing"or"upgrade_needed", the project's settings or installed Spektacular files are out of date: relay the response'sactionmessage to the user, ask them to rungo run . migrate(they can preview it withgo run . migrate --dry-run), and wait for their decision before continuing.- On
"unsupported_format", relay theactionmessage: the project was written by a newer Spektacular, which the user must install before continuing.- Never run
migrateorinit, and never modify installed files yourself. Upgrading is always an explicit, user-initiated action.
What this skill does
This skill orchestrates the existing go run . knowledge CRUD surface for ad-hoc read, contribute, update, and audit operations on the project's knowledge store, without starting a spec/plan/implement flow. Unlike spek-new, spek-plan, and spek-implement, it does not drive an interactive CLI state machine — it is a static playbook. The agent recognises the user's natural-language intent, picks one of four branches (lookup / contribute / update / audit), and calls the matching go run . knowledge command directly.
When to invoke
Invoke this skill any time the user references the knowledge base, an entry, a convention worth remembering, or asks a question that the knowledge store might already answer. Typical natural-language triggers include:
- "What do we know about X?"
- "Search the knowledge base for Y."
- "Remember that Z is the case." / "Add a note about Z."
- "Update what we have on W."
- "Recall the convention for V."
- "Check the tags on our entries." / "Are our knowledge entries tagged properly?"
One skill handles all four intents. Discriminate by what the user actually said — do not ask the user to pick a slash command per intent.
Intent: lookup
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 Changed · +1 lines 385896290c7b
- 1mo ago Changed · +49 lines 8f00457590be
- 1mo ago Changed · +1 lines 7f20b2904678
- 1mo ago First seen · 83 lines · 17 tokens per session scan A 4960cc2c348a
spek-knowledge is a skill published in the GitHub repository jumppad-labs/spektacular (20 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 3,993 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-08-30.
Other skills, from other repositories
gsd-graphify
Build, query, and inspect the project knowledge graph in .planning/graphs/.
gsd-mempalace-capture
File a phase artifact into MemPalace; mirror decision facts into its temporal KG.
gsd-mempalace-recall
Recall decisions, patterns, and surprises from MemPalace before planning.
project-knowledge
Verified, actionable gotchas for oh-my-posh. Read the matching topic file BEFORE changing shell integration scripts (pwsh, zsh, bash, fish, cmd/Clink, nu, elvish, xonsh), terminal or pty behavior, WSL or e2e shell tests, Go internals (cache, segments, streaming, serve daemon, template rendering, output sanitization)…
gsd-thread
Manage persistent context threads for cross-session work.
kiro-steering-custom
Create custom steering documents for specialized project contexts.