tech

A technical-analysis agent for turning product requirements into engineering constraints, possible approaches, risks, and a recommendation.

In plain words
What is it for?
Use it during the technical-analysis stage before implementation, when no source code should be changed.
Why use it?
It separates technical planning from coding and records relevant project guidance and known problems.

Agent

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 agents/shenchangmin/cairnkit/tech
Clone the repo
git clone --depth 1 https://github.com/shenchangmin/cairnkit
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 309 The whole file, excluding the scripts and references it only reads on demand.
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.00051 $0.00309
Opus 5 $0.00026 $0.00154
Sonnet 5 $0.00010 $0.00062
Haiku 4.5 $0.00005 $0.00031

Measured yesterday against content hash bbb5eb1a86b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tech 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 yesterday.

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/tech.md · 32 lines

What it actually says

tech (role agent)

You produce the technical analysis for one run. One artifact, then return. No code.

Red lines

  • Do not write or modify source code.
  • Write only the artifact below.

Knowledge loop (required)

Before writing, run cairn --root . kb query --stage ANALYSE_TECH --budget 300. Apply relevant entries; record a knowledgeReferences block (id/title/usedIn) at the end of the artifact. Querying without recording counts as "not used".

Task

Read docs/workflows/<run-id>/01-product.md, then write docs/workflows/<run-id>/02-tech.md:

  1. Constraints — platform, dependencies, performance, compatibility.
  2. Options — candidate approaches with pros/cons.
  3. Pitfalls — known traps (cite knowledge entries where they apply).
  4. Recommended approach + rationale.
  5. knowledgeReferences block.

<run-id> is in .cairnkit/STATE.yaml. Return a one-line summary; the orchestrator advances.

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. yesterday First seen · 32 lines · 51 tokens per session scan A bbb5eb1a86b0

Subscribe to this mod's changes

tech is an agent published in the GitHub repository shenchangmin/cairnkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 309 once invoked, about $0.0003 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-31.

Related

Other agents, from other repositories

backend-go-engineer

Use this agent when you need to develop, modify, or troubleshoot Go backend code, including API endpoints, database operations, middleware, authentication, or any server-side functionality. Examples: Context: User needs to add a new API endpoint for user preferences. user: 'I need to add an endpoint to save user…

Zettelgarden/Zettelgarden · 204 tokens

code-reviewer

Use this agent when you need to review code changes, pull requests, or newly written code for quality, best practices, and potential issues. Examples: Context: The user has just written a new React component for the Zettelgarden frontend. user: 'I just finished implementing the CardEditor component with markdown…

Zettelgarden/Zettelgarden · 168 tokens

frontend-ticket-implementer

Use this agent when you need to implement frontend features, fix bugs, or complete development tickets for the React/TypeScript frontend. Examples: Context: User has a ticket to implement a new card creation modal component. user: 'I need to implement ticket FE-123: Add a modal for creating new cards with title…

Zettelgarden/Zettelgarden · 227 tokens

ui-ux-designer

Use this agent when you need UI/UX design guidance, component design decisions, user experience improvements, accessibility recommendations, or design system advice. Examples: Context: User is working on improving the card creation interface in Zettelgarden. user: 'The card creation form feels clunky and users are…

Zettelgarden/Zettelgarden · 214 tokens

knowledge-guide

Proactive methodology guidance agent. Monitors note creation and provides real-time quality advice. Suggests connections, flags quality issues, recommends MOC updates. Activates when the user creates notes, asks about methodology, or needs architectural advice.

agenticnotetaking/arscontexta · 50 tokens

rust-release-engineer

Use this agent when a task involves designing, implementing, debugging, or maintaining CI/CD pipelines for Rust projects on GitHub Actions, including multi-platform builds for Linux, macOS, and Windows, release workflows, artifact publishing, Homebrew packaging, and Linux distribution packages such as deb or rpm. Do…

ractive/hyalo · 85 tokens