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/sparknpx skills add devnomad-byte/techneering --skill sparkgit 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.00035 | $0.01613 |
| Opus 5 | $0.00017 | $0.00807 |
| Sonnet 5 | $0.00007 | $0.00323 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
spark 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sparking Ideas Into Designs
Help turn ideas into fully formed designs through natural collaborative dialogue. Explore intent, refine requirements, compare approaches — then hand off to draft for formal documentation.
Core Principle
NO IMPLEMENTATION WITHOUT A DESIGN.
Present a design and get user approval before writing any code.
Steps
Step 1: Explore Project Context
Check files, docs, recent commits. Understand the current state before asking questions.
For existing projects (code already exists):
1a. Project Structure Analysis
- Scan directory structure, identify layering pattern (MVC / layered / feature-based / modular / monorepo)
- Identify file/directory naming convention (kebab-case / PascalCase / camelCase / snake_case)
1b. Code Pattern Analysis
Sample 3-5 source files and identify:
- Naming conventions: files, classes, functions, constants, variables (camelCase / snake_case / PascalCase / UPPER_SNAKE)
- Error handling: exceptions / Result type / error codes / try-catch
- Dependency injection: constructor / annotations / manual / module system
- API style: REST / GraphQL / gRPC (if applicable)
- Data access: ORM / query-builder / raw-sql / repository pattern
- Import style: alias (@/) / relative / absolute / package-based
1c. Formatting Style Analysis
- Check for config files:
.editorconfig,.prettierrc,.eslintrc,biome.json - If no config found, infer from code: indent (tab/space, 2/4), quotes (single/double), semicolons, trailing commas
1d. Summarize Conventions
Produce a coding_conventions summary as part of spark output. This will be written to techneering/config.yaml by tn:draft.
1e. Tech Stack Detection & Quality Standards Recommendation
Detect project tech stack from build files and recommend matching quality standards:
| Detected File | Tech Stack | Recommended Source |
|---|---|---|
pom.xml / build.gradle |
Java | ali-taishan-java |
requirements.txt / pyproject.toml |
Python | ali-taishan-python + pep8 |
go.mod |
Go | gofmt |
package.json + vue |
Vue | vue-official |
package.json + react |
React | react-airbnb |
package.json + typescript |
TypeScript | google-js |
package.json (other) |
JavaScript | prompt user to choose |
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 · 157 lines · 35 tokens per session scan A 5a871d9a1a01
spark is a skill published in the GitHub repository devnomad-byte/techneering (13 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,613 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-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…