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 agentmods add skills/wufunc/nova/adr-creatornpx skills add wufunc/nova --skill adr-creatorgit clone --depth 1 https://github.com/wufunc/novaWhat 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 | $0.00072 | $0.00961 |
| Opus 5 | $0.00036 | $0.00481 |
| Sonnet 5 | $0.00014 | $0.00192 |
| Haiku 4.5 | $0.00007 | $0.00096 |
Grade A, and why
adr-creator 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 3d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR Creator
Overview
Pure writer skill that creates Architecture Decision Records. Always invoked by the memory skill, never directly for decision-making. Receives the session context where architectural decisions were made and generates properly formatted ADR files.
Workflow
Step 1: Determine ADR Number
# List existing ADRs to find the highest number
Glob pattern: .nova/memory/adr/[0-9]*.md
# Use next sequential three-digit number (001, 002, 003...)
Step 2: Determine Memory Tag
# Find the latest mem tag to determine next number
git tag -l 'mem/*' --sort=-version:refname | head -1
# Next tag: mem/NNN (increment by 1)
# If no tags exist, use mem/001
If the memory skill has already provided a tag name (because a DevLog is also being created in this session), use that same tag.
Step 3: Generate ADR Content
Analyze the conversation to extract the architectural decision. Follow the format in references/adr-format.md.
Structure:
---
tags: [tag1, tag2, tag3]
modules: [path/to/module1, path/to/module2]
summary: "One-line summary of the decision for Grep-based retrieval"
tag: mem/NNN
---
# ADR NNN: Concise Decision Title
## Date
YYYY-MM-DD HH:mm
## Background
- Problem description
- Why a decision was needed
- Technical constraints
- Alternative approaches considered
## Decision
- Chosen approach
- Key implementation points
- Design rationale (why this approach, why not others)
## Consequences
### Advantages
- Positive impacts
### Disadvantages
- Negative impacts and trade-offs
### Risk Mitigation (optional)
- How to reduce negative impacts
## Related Decisions
- ADR XXX: Reference to related decisions
Content Guidelines:
- Title (max 10 words): Concise description of the decision
- YAML Frontmatter: Must include tags, modules, summary, tag (for Grep-based retrieval)
- Background: Explain the "why", list alternatives considered
- Decision: State what was chosen and justify why
- Consequences: Be honest about both advantages and disadvantages
- Related Decisions: Reference other ADRs if applicable (use "None" if none)
What ships with it
2 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.
- 3d ago First seen · 138 lines · 72 tokens per session scan A 3ab79ac90080
adr-creator is a skill published in the GitHub repository wufunc/nova (2 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 961 once invoked, about $0.0004 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
telnyx-ai-inference-curl
Access Telnyx LLM inference APIs, embeddings, and AI analytics for call insights and summaries. This skill provides REST API (curl) examples.
telnyx-ai-assistants-go
AI voice assistants with custom instructions, knowledge bases, and tool integrations.
telnyx-email-domains-curl
Manage email sending domains, verify DNS records (SPF, DKIM, DMARC, MX), check domain health, and configure domain-level webhooks for delivery events.
telnyx-email-inbound-curl
Manage email inboxes, list and search inbound messages, threads, sender filters, and reply to or forward messages. Use for building email agents that read and respond to incoming email.
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.
telnyx-numbers-compliance-curl
Manage regulatory requirements, number bundles, supporting documents, and verified numbers for compliance. This skill provides REST API (curl) examples.