techne AGENTS.md

A repository instruction file for Techne, an early collection of coding-agent skills and plugin integrations. It records project facts, working rules, and the development workflow.

In plain words
What is it for?
Use it when changing Techne's skills, plugin skins, installation documentation, or validation scripts.
Why use it?
It provides the current project context so an agent does not mistake old code or documentation for the active architecture.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/lynxlangya/techne/agents-md
Clone the repo
git clone --depth 1 https://github.com/lynxlangya/techne

Made for: Codex, OpenCode.

Per session 1,237 This file is loaded in full into every session.
When invoked 1,237 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01237 $0.01237
Opus 5 $0.00619 $0.00619
Sonnet 5 $0.00247 $0.00247
Haiku 4.5 $0.00124 $0.00124

Measured 2d ago against content hash 107f8596cd0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

techne AGENTS.md 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.

AGENTS.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

version: v0.1
project: techne
updated: 2026-07-02

Project Facts

  • techne is an early-stage skills/plugin repository for "Skills and agents for the AI era."
  • The current main branch contains the Claude plugin skin, install matrix docs, Cursor/Gemini thin skins, and four real skills: skills/anchor-viz (typed diagram router with a mechanical provenance gate), skills/anchor-repro (repro-first bugfix ledger), skills/anchor-vet (evidence-gated diff review), and skills/anchor-intake (written-brief interrogation gate).
  • There is still no root app, root package manager, CI, or general test runner. skills/anchor-viz/scripts/package.json is a local helper manifest for the Mermaid validator, not a repo-wide build system; skills/anchor-repro/scripts/repro_ledger.py, skills/anchor-vet/scripts/vet_gate.py, and skills/anchor-intake/scripts/intake_gate.py are dependency-free Python 3 stdlib (POSIX-only).
  • The git history contains a legacy atools-js codebase, but new work in this repo should not infer current architecture, tooling, or business rules from that legacy history unless the user explicitly asks for migration or reference work.

Working Rules

  • Start with current files, not assumptions: inspect the present tree before choosing a structure, dependency, or framework.
  • Keep early changes content-first and minimal. Do not add scaffolding, package managers, CI, telemetry, network services, or generated boilerplate unless the task requires them.
  • When adding skills, agents, docs, or examples, include the intended usage, constraints, and a direct validation path.
  • Prefer small, reviewable directory structures over broad future-facing abstractions until the repo has repeated patterns.
  • Keep one tool-neutral skill body in skills/; host-specific files should stay as thin skins or install instructions that point back to that body.
  • Keep public-facing documentation split by language: README.md is the default English document, and README-CN.md is the Chinese companion. For real skills, keep executable instructions in SKILL.md and human usage guidance in nearby README.md / README-CN.md files.
  • Do not commit generated .techne/ viewer output. skills/anchor-viz/scripts/build_viewer.py writes .techne/viz/index.html inside target projects only.
  • Do not commit secrets, tokens, private config, .env contents, or logs that may contain credentials.

Read the full file on GitHub · 46 lines

Changes

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.

  1. 2d ago First seen · 46 lines · 1,237 tokens per session scan A 107f8596cd0d

Subscribe to this mod's changes

techne AGENTS.md is an instructions file published in the GitHub repository lynxlangya/techne (105 stars, last pushed 2mo ago), licensed MIT. It adds 1,237 tokens to every session, about $0.0062 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.