Borrowing it
Nothing to install: this file belongs to novasamatech/nova-spektr. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/novasamatech/nova-spektr/dev/.claude/skills/feature-specs/SKILL.mdgit clone --depth 1 https://github.com/novasamatech/nova-spektrWrote 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/novasamatech/nova-spektr/feature-specs)<a href="https://agentmods.dev/skills/novasamatech/nova-spektr/feature-specs"><img src="https://agentmods.dev/badge/skills/novasamatech/nova-spektr/feature-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/novasamatech/nova-spektr/feature-specs"><img src="https://agentmods.dev/badge/skills/novasamatech/nova-spektr/feature-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.01095 |
| Opus 5 | $0.00024 | $0.00548 |
| Sonnet 5 | $0.00010 | $0.00219 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
feature-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 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Specs & Feature Map Maintenance
Non-trivial features (src/renderer/features/) and aggregates (src/renderer/aggregates/) carry a colocated
README.md — a product spec of what the code does and why (states, scenarios, lifecycle), not how it is wired. All
specs are indexed in the Feature Map: src/renderer/features/README.md.
The canonical human-facing convention (what goes in a spec, the author-approval workflow) is
docs/content/docs/code/style/feature-specs.md — read it before writing a spec. Worked example:
src/renderer/aggregates/multisig-operation-description/README.md.
When a spec is required
- New feature/aggregate with user-visible behaviour or non-obvious rules → write one.
- Material behaviour change (new states, new gating, changed flow) → update the existing spec in the same change.
- Skip for trivial, presentation-only, or purely mechanical modules.
- Before changing any feature: read its README first if it exists — it is the source of product truth. If the code contradicts it, surface that.
- A draft spec must be approved by the feature's author before the change is finalized — treat the spec as a deliverable alongside the code.
Spec README structure
Use the template from the canonical convention doc (docs/content/docs/code/style/feature-specs.md, section "Template")
— do not restate it here; the doc is the single source for the spec's structure.
One addition the template already includes but is easy to miss: the backlink line is mandatory, sits right after the
# Title heading, and carries the Last reviewed date:
> Part of the [Feature Map](../README.md) — Last reviewed: YYYY-MM-DD
(from aggregates/<name>/ the path is ../../features/README.md). Match the depth to the feature — a small one needs
only Overview + States.
Date rules (stamp with today's date, date +%F):
- Creating a spec → set the date.
- Updating a spec → bump the date.
- Changing a module's code while the spec stays accurate → re-read the spec, confirm it still matches, bump the date — the bump is the record that the spec was re-reviewed. CI fails the PR if module code changed and the date did not move.
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 First seen · 96 lines · 49 tokens per session scan A 3d734dc27480
feature-specs is a skill published in the GitHub repository novasamatech/nova-spektr (56 stars, last pushed 8d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,095 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-09-01.
Other skills, from other repositories
implementer
Implement changes following an existing PLAN.md. Validates scope, writes code, and self-reviews before handoff.
architect
Design implementation plan for non-trivial changes. Loads relevant architecture docs, asks clarifying questions, and produces a PLAN.md.
reviewer
Review a PR or diff against architecture and code checklists. Produces a verdict with blocking/major/minor findings.
commit-message
Generate a well-structured commit message from staged changes.
blockchain-web3
Use this skill when asked about web3 frontend development, ethers.js, viem, wagmi, web3.js, wallet integration (MetaMask, Phantom, WalletConnect), dApp architecture, RPC providers (Alchemy, Infura), and TypeScript blockchain SDKs. Language: TypeScript. Covers reading blockchain state, sending transactions, wallet…
frontend-design
Create distinctive, production-grade Stellar dApp UI. Combines bold aesthetic direction with smart contract integration patterns — wallet connection flows, transaction UX, contract data displays, and agentic kit hook wiring. No generic "AI slop" aesthetics.