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/auditnpx skills add devnomad-byte/techneering --skill auditgit 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.01293 |
| Opus 5 | $0.00014 | $0.00647 |
| Sonnet 5 | $0.00006 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
audit 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Implementation
Dual-layer verification: does the code match the spec, and does the code solve the real problem?
Core Principle
NO COMPLETION WITHOUT VERIFICATION.
Every requirement traced. Every decision checked. Every gap documented.
Steps
Step 1: Select the Change
Same selection logic as tn:forge — auto-detect or ask user.
Always announce: "Verifying change: "
Step 2: Load All Artifacts
Read:
techneering/changes/<name>/proposal.md— for "Why" (Layer 2)techneering/changes/<name>/specs/**/*.md— for requirements (Layer 1)techneering/changes/<name>/design.md— for architecture decisions (Layer 1)techneering/changes/<name>/tasks.md— for task completion check
Step 3: Layer 1 — Code ↔ Spec Compliance
3a. Completeness Check
- Parse
tasks.md: count- [ ](incomplete) vs- [x](complete) - If incomplete tasks exist → CRITICAL
- Extract all requirements from delta specs (
### Requirement:headers) - For each requirement, search codebase for implementation evidence
- If requirements appear unimplemented → CRITICAL
3b. Correctness Check
- For each requirement from specs:
- Search codebase for implementation
- Assess if implementation matches requirement intent
- If divergence → WARNING
- For each scenario (
#### Scenario:):- Check if conditions are handled in code
- Check if tests exist covering the scenario
- If uncovered → WARNING
3c. Coherence Check
- If design.md exists:
- Extract key decisions
- Verify implementation follows those decisions
- If contradiction → WARNING
- Review new code for consistency with project patterns
- If significant deviations → SUGGESTION
Step 4: Layer 2 — Code ↔ Real Requirements
- Read the Why section of proposal.md
- Trace back from the code to the original problem statement
- Ask: Does this implementation actually solve the original problem?
- Check if the "What Changes" in proposal.md are all addressed
- If the implementation solves a different problem than stated → CRITICAL
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 · 154 lines · 28 tokens per session scan A 5ab871e9decf
audit 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 1,293 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.
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.
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.
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…