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/devnomad-byte/techneering/vaultnpx skills add devnomad-byte/techneering --skill vaultgit clone --depth 1 https://github.com/devnomad-byte/techneeringWhat 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.00028 | $0.00918 |
| Opus 5 | $0.00014 | $0.00459 |
| Sonnet 5 | $0.00006 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
vault 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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive a Change
Merge delta specs into main specs and move the change to archive. The final step in the Techneering workflow.
Core Principle
NO ARCHIVE WITHOUT CONFIRMATION.
Every artifact checked. Every delta applied. Every conflict reported.
Steps
Step 1: Select the Change
Same selection logic as tn:forge — auto-detect or ask user.
Always announce: "Archiving change: "
Step 2: Pre-Archive Checks
Artifact completion: Check all artifacts exist (proposal, specs, design, tasks).
Task completion: Read techneering/changes/<name>/tasks.md, count - [ ] (incomplete) vs - [x] (complete).
- If incomplete tasks: warn user, confirm before proceeding
Step 3: Delta Spec Merge
If delta specs exist at techneering/changes/<name>/specs/:
3a. Read Delta Specs
For each delta spec file, parse the delta blocks:
## ADDED Requirements## MODIFIED Requirements## REMOVED Requirements## RENAMED Requirements
3b. Apply Deltas to Main Specs
Execute operations in this strict order: RENAMED → REMOVED → MODIFIED → ADDED
- ADDED: Append requirement blocks to the end of the corresponding chapter in the main spec
- MODIFIED: Replace the matching requirement block in the main spec (match by
### Requirement: <name>) - REMOVED: Delete the matching requirement block from the main spec
- RENAMED: Rename the requirement block header in the main spec (FROM → TO)
3c. Handle Edge Cases
- MODIFIED/REMOVED target not found in main spec → Skip, log warning
- ADDED target chapter doesn't exist → Create chapter, then append
- Conflict (same requirement targeted by multiple deltas) → Stop merge, report to user
3d. Post-Merge Verification
- Confirm main spec structure is intact
- No orphaned references
- No duplicate requirement names
If no delta specs exist, skip merge step.
Step 4: Perform Archive
mkdir -p techneering/archive
mv techneering/changes/<name> techneering/archive/YYYY-MM-DD-<name>
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.
- 2d ago First seen · 122 lines · 28 tokens per session scan A 97cec9666c99
vault is a skill published in the GitHub repository devnomad-byte/techneering (13 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 918 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
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
workflows
Execute a workflow script that orchestrates multiple subagents deterministically. Use when the user explicitly requests a workflow, multi-agent orchestration, parallel or sequential agent pipelines, structured agent outputs, or a durable background workflow run.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
office-hours
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to…