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/affectionatec/agentic-engineering/using-agentic-engineeringnpx skills add affectionatec/agentic-engineering --skill using-agentic-engineeringgit clone --depth 1 https://github.com/affectionatec/agentic-engineeringWhat 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.00115 | $0.00902 |
| Opus 5 | $0.00057 | $0.00451 |
| Sonnet 5 | $0.00023 | $0.00180 |
| Haiku 4.5 | $0.00012 | $0.00090 |
Grade A, and why
using-agentic-engineering 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Agentic Engineering — The Router
You are the router for the Agentic Engineering documentation chain. Your job: figure out where this project stands in the chain, brief the user, and hand off to the right skill. Do not start producing documents yourself — route.
Step 1: Assess the project
Check which chain documents exist (use file search/read tooling; adjust paths if AGENTS.md declares different ones):
| Document | Default path |
|---|---|
| AGENTS.md | AGENTS.md (repo root) |
| PRD | docs/prd.md |
| SPEC | docs/spec/*.md |
| ADR | docs/adr/ADR-*.md |
| IMPL PLAN | docs/plans/implementation-plan.md |
| STATUS | docs/status.md |
| VERIFICATION LOG | docs/verification-log.md |
If AGENTS.md exists, read it first — it is the single source of truth and may override everything below.
If docs/status.md exists, read it: check the In-Flight Checkpoint (a non-none value means the last session crashed — recovery is the first priority) and the latest handoff log entry.
Step 2: Report the position
Present a compact table: each chain document, whether it exists, and its state (e.g., SPEC count, last STATUS entry date, open task from the latest handoff). Three to five lines of prose maximum around it — this is a briefing, not an essay.
Step 3: Route
Recommend exactly one next move, based on the first gap in the chain:
| Situation | Route to |
|---|---|
| Substantial existing codebase, but no/partial chain docs | existing-project-onboarding — reverse-engineer the as-built chain first (it bootstraps AGENTS.md too) |
No AGENTS.md (little or no code yet) |
agents-md-template — bootstrap the single source of truth first |
| No PRD and the user has a rough idea | project-kickoff-prd — phased dialogue to a prioritized PRD |
| PRD exists, no specs for the target scope | technical-specification — harden the PRD into contracts |
| A decision fork is on the table ("X or Y?") | architecture-decision-record — capture it before it evaporates |
| Specs approved, no implementation plan | implementation-plan — dependency-ordered atomic tasks |
| Plan exists and a session is starting | status-tracker — read the briefing, pick the next unblocked task |
| Code work is starting, or a built task needs to ship | git-workflow — branch per task, draft PR carrying the done condition |
| A task claims completion / anything sits at 🔍 | independent-verification — a fresh-context verdict (bundled verifier sub-agent where available) |
| A conversation decision makes a chain doc stale, or the user proposes a new feature / scope change | documentation-maintenance — flag the drift, propose the gated update, route the change through the chain |
In-Flight Checkpoint is not none |
status-tracker — crash recovery from the checkpoint |
| The user wants multiple tasks run unattended | run-loop — the chain-aware loop driver (verify-gated, never merges) |
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.
- yesterday First seen · 54 lines · 115 tokens per session scan A ca600b7b49db
using-agentic-engineering is a skill published in the GitHub repository affectionatec/agentic-engineering (4 stars, last pushed 2mo ago), licensed MIT. It adds 115 tokens to every session and 902 once invoked, about $0.0006 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.
Other skills, from other repositories
vibe-to-agentic-framework
The conceptual framework behind the presentation — what "Vibe Coding to Agentic Engineering" means, why the journey is structured the way it is, and how every slide fits the narrative arc.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…
presentation-structure
Knowledge about the presentation slide format, weight system, navigation, and section structure.
presentation-styling
Knowledge about CSS classes, component patterns, and syntax highlighting in the presentation.
weather-fetcher
Instructions for fetching current weather temperature data for Dubai, UAE from Open-Meteo API.
time-skill
Display the current time in Pakistan Standard Time (PKT, UTC+5). Use when the user asks for the current time, Pakistan time, or PKT.