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 skills add Plazmodium/odin-workflow --skill generic-devgit clone --depth 1 https://github.com/Plazmodium/odin-workflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/plazmodium/odin-workflow/generic-dev)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/generic-dev"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/generic-dev.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00020 | $0.02254 |
| Opus 5 | $0.00010 | $0.01127 |
| Sonnet 5 | $0.00004 | $0.00451 |
| Haiku 4.5 | $0.00002 | $0.00225 |
Grade A, and why
generic-dev 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 6d 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generic Software Development
Overview
This skill provides universal software development principles that apply across all languages, frameworks, and platforms. Use this as a fallback when specific tech stack skills are not available, or as a foundation that complements specialized skills.
When This Skill Applies
- No specific framework/language skills match the project's tech stack
- Building from scratch without established patterns
- Working with unfamiliar or legacy codebases
- General architectural decisions before tech stack selection
Core Principles
SOLID Principles
| Principle | Description | Application |
|---|---|---|
| Single Responsibility | One class/module = one reason to change | Split large files by concern |
| Open/Closed | Open for extension, closed for modification | Use interfaces and composition |
| Liskov Substitution | Subtypes must be substitutable for base types | Don't break contracts in subclasses |
| Interface Segregation | Many specific interfaces > one general interface | Split large interfaces |
| Dependency Inversion | Depend on abstractions, not concretions | Inject dependencies, use interfaces |
DRY, KISS, YAGNI
- DRY (Don't Repeat Yourself): Extract repeated logic into functions/modules
- KISS (Keep It Simple): Prefer simple solutions over clever ones
- YAGNI (You Aren't Gonna Need It): Don't build features "just in case"
Code Organization
File Structure Patterns
src/
├── index.{ext} # Entry point
├── config/ # Configuration loading
├── types/ # Type definitions
├── utils/ # Pure utility functions
├── services/ # Business logic
├── repositories/ # Data access layer
├── controllers/ # Request handlers (if applicable)
├── middleware/ # Cross-cutting concerns
└── tests/ # Test files (or alongside source)
Naming Conventions
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.
- 6d ago First seen · 308 lines · 20 tokens per session scan A 01ee71cb9525
generic-dev is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 2,254 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-09-01.
Other skills, from other repositories
b123d-edit
Use this skill when the task is to change an existing build123d model or script: "make this bracket 5 mm taller", "move the holes inward", "add a counterbore", "remove this rib", "make it fit this mating part", or "repair the code so the intended edit remains parametric".
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
mlflow-traces
Use when working with MLflow traces: debugging via MCP tools, analyzing performance, logging feedback, writing custom scorers/evaluations, or cleaning up trace data.
gemini-visualize
Generates interactive HTML visualizations (concept maps, evidence networks, knowledge graphs) from Gemini analysis results. Triggers automatically after /gr:video, /gr:research, /gr:analyze.
video-explainer
Teaches Claude how to use the 15 video explainer tools to create explainer videos from research content. Activates when working with video synthesis, explainer creation, or the video-explainer MCP server.
workflows
Knowledge about ComfyUI workflow API format, node connections, and common patterns. Use when helping users build, modify, or understand workflows.