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/lynxlangya/techne/_templatenpx skills add lynxlangya/techne --skill _templategit clone --depth 1 https://github.com/lynxlangya/techneWhat 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.00022 | $0.00396 |
| Opus 5 | $0.00011 | $0.00198 |
| Sonnet 5 | $0.00004 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
_template 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.
What it actually says
Skill Title
Use this file as the starting point for a new techne skill. Keep the skill body tool-neutral: the guidance here should make sense outside any one host, with tool-specific loading handled by plugin manifests.
Quality Bar
A techne skill must force a move the model can make but often skips. It is not a place to restate common knowledge, collect vague advice, or duplicate what the platform or superpowers already handles well.
Before authoring, identify:
- The skipped move this skill forces.
- The failure pattern it prevents.
- The cases where the skill should not apply.
- The observable improvement expected when the skill is present.
When To Use
State the triggering situation in concrete terms. Prefer user intents, task conditions, and failure signals over broad domain labels.
Instructions
Write the smallest set of instructions that reliably forces the move. Use direct commands, checks, and stop conditions. Avoid product-specific paths, local tool names, or host-only features unless they are documented as optional references.
Validation
Each real skill should include an eval.md alongside SKILL.md. The eval file
records the empirical acceptance test from WORKFLOW.md: baseline behavior,
with-skill behavior, what counts as improvement, and the pass bar.
For scaffold-only or template changes, direct mechanical validation is enough.
Supporting Files
Optional files live next to SKILL.md when they remove noise from the main
skill:
eval.mdfor the empirical acceptance test.scripts/for executable helpers the model may run.reference.mdfor longer material loaded only when needed.
Do not add empty support folders. Add them only when the skill actually needs them.
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 · 56 lines · 22 tokens per session scan A 2027686a8188
_template is a skill published in the GitHub repository lynxlangya/techne (105 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 396 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
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.