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/forgenpx skills add devnomad-byte/techneering --skill forgegit 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.00023 | $0.01004 |
| Opus 5 | $0.00012 | $0.00502 |
| Sonnet 5 | $0.00005 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
forge 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge a Change
Implementation entry point. Load change artifacts, then chain to tn:blueprint for task breakdown and tn:assemble for execution.
Core Principle
READ ALL CONTEXT BEFORE WRITING ANY CODE.
Load every artifact. Understand the full picture. Then implement.
Steps
Step 1: Select the Change
If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a change
- Auto-select if only one active change exists in
techneering/changes/ - If ambiguous, list all active changes with progress info and ask the user to select
Always announce: "Using change: "
Step 2: Load Context
Read all artifacts from the change directory:
techneering/changes/<name>/proposal.mdtechneering/changes/<name>/specs/**/*.mdtechneering/changes/<name>/design.mdtechneering/changes/<name>/tasks.md
Also read techneering/config.yaml for project context.
Step 3: Show Current Progress
Parse tasks.md for checkboxes: - [ ] (pending) vs - [x] (complete).
Display:
- Change name and schema
- Progress: "N/M tasks complete"
- Remaining tasks overview
Step 4: Create Implementation Plan (tn:blueprint)
Invoke the tn:blueprint skill to break down the tasks into bite-sized implementation steps:
- Exact file paths
- Complete code for each step
- Verification commands with expected output
- No placeholders
Step 5: Execute with Assemble (tn:assemble)
Invoke the tn:assemble skill to execute the plan:
- Each task gets a fresh subagent
- Two-stage review per task: spec compliance → code quality
- Independent tasks can run in parallel (max 3 concurrent)
- Follow
tn:redgreenfor each task (red-green-refactor) - Use
tn:diagnoseif issues arise
Step 6: Track Progress
After each task completes:
- Mark the corresponding checkbox in tasks.md:
- [ ]→- [x] - Report progress: "Task N/M complete"
Step 7: On Completion
Display:
## Implementation Complete
**Change:** <change-name>
**Progress:** N/N tasks complete
### Completed This Session
- [x] Task 1
- [x] Task 2
...
All tasks complete! Proceed to tn:gate to verify.
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 · 143 lines · 23 tokens per session scan A 970d0d966f8a
forge is a skill published in the GitHub repository devnomad-byte/techneering (13 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 1,004 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…