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 Hipson47/Hipson --skill hipson-workflowgit clone --depth 1 https://github.com/Hipson47/HipsonWrote 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/hipson47/hipson/hipson-workflow)<a href="https://agentmods.dev/skills/hipson47/hipson/hipson-workflow"><img src="https://agentmods.dev/badge/skills/hipson47/hipson/hipson-workflow.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.00041 | $0.01314 |
| Opus 5 | $0.00020 | $0.00657 |
| Sonnet 5 | $0.00008 | $0.00263 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
hipson-workflow 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 3d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hipson-workflow
Purpose
Universal AI-assisted development workflow for Codex. Use it to run structured software work with clear roles, portable prompts, focused implementation, and reliable review.
Agent-Native Entry Point
For non-trivial repo tasks, run hipson work --task "..." first. It builds a
provider-free Codex work brief with the route, redacted scan, packet command,
verification commands, memory/handoff command, curated skills, and audit
contract. Use hipson route --task "..." when only the lower-level routing
decision and safe commands are needed.
Codex-First Hermes Bridge
Codex remains the user's primary control surface. Do not require the user to talk to Hermes for normal software work.
Use hipson hermes intake --project <repo> --task "<task>" only when the task
benefits from Hermes-side status tracking, scheduling, Telegram/gateway
dispatch, or cross-session bus events. For ordinary coding, review, verification,
and packet generation, route through hipson work --task "..." or
hipson route --task "..." directly.
When To Use
- Starting a new project.
- Reviewing an existing repo.
- Creating implementation prompts for another agent.
- Running two Codex sessions.
- Refactoring or productizing features.
- Building project-specific
AGENTS.mdfiles.
When Not To Use
- Tiny one-line edits.
- Pure non-code writing tasks.
- Tasks where the user explicitly wants a quick answer only.
Core Workflow
- Intake: restate the goal, constraints, risks, and expected output.
- Work brief: run
hipson work --task "..."for the default route -> scan -> packet/execute -> verify -> memory/handoff contract. - Context map: identify relevant files, ownership boundaries, dependencies, and unknowns.
- Plan: define small implementation steps and verification points.
- Task packet: create a bounded prompt for Executor when delegation is useful.
- Execution: implement minimal diffs that satisfy the task packet.
- Verification: run real commands and record exact outcomes.
- Review: inspect diff for correctness, regressions, tests, maintainability, and security.
- Context folding: summarize outcome, files changed, verification, risks, and next task.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 188 lines · 41 tokens per session scan A 6d182312e346
hipson-workflow is a skill published in the GitHub repository Hipson47/Hipson (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,314 once invoked, about $0.0002 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-03.
Other skills, from other repositories
sc-skill
Capture deterministic macOS screenshots for testing, docs, release notes, and marketing assets. Use when asked to automate app screenshots, batch-generate screenshot sets, standardize window sizing/composition, or choose between Peekaboo and native macOS screenshot tooling.
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
agent-session-format-check
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.
agent-support-matrix
Maintain Agent Sessions agent support matrix and JSON/JSONL parsing compatibility. Use when checking upstream agent releases for session format changes, updating max verified versions in docs/agent-support/agent-support-matrix.yml, or updating docs/agent-json-tracking.md and fixtures/tests.
kirby-collections-and-navigation
Builds Kirby listings, pagination, search, filtering/sorting/grouping, and navigation menus. Use when implementing collection logic in templates/controllers/snippets.
kirby-debugging-and-tracing
Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.