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/apexiq/skillsmith/agentic_workflownpx skills add ApexIQ/skillsmith --skill agentic_workflowgit clone --depth 1 https://github.com/ApexIQ/skillsmithWrote 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/apexiq/skillsmith/agentic_workflow)<a href="https://agentmods.dev/skills/apexiq/skillsmith/agentic_workflow"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/agentic_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.00032 | $0.01036 |
| Opus 5 | $0.00016 | $0.00518 |
| Sonnet 5 | $0.00006 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
agentic-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 6d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔄 Agentic Workflow
Philosophy: Agents gather context, take action, verify, and iterate until the goal is achieved.
The Agentic Loop
Based on Anthropic's agent design patterns:
┌─────────────────────────────────────────────┐
│ │
│ 1. GATHER CONTEXT │
│ └─ Read files, search, understand task │
│ │
│ 2. TAKE ACTION │
│ └─ Write code, run commands, edit files │
│ │
│ 3. VERIFY RESULTS │
│ └─ Run tests, check output, validate │
│ │
│ 4. ITERATE OR COMPLETE │
│ └─ If not done, return to step 1 │
│ │
└─────────────────────────────────────────────┘
Core Principles
1. Start Simple
- Begin with a single-agent system.
- Add complexity only when needed.
- Maximize one agent's capabilities before adding more.
2. Clear Tool Contracts
Each tool should have:
- Clear input: What parameters it accepts
- Clear output: What it returns
- Error handling: What happens on failure
# Good tool definition
def search_codebase(query: str, file_pattern: str = "*") -> list[SearchResult]:
"""
Search codebase for matching code.
Args:
query: Text or regex to search for
file_pattern: Glob pattern to filter files (default: all)
Returns:
List of SearchResult with file, line, and content
Raises:
SearchError: If query is invalid regex
"""
3. Verification Before Completion
Never assume success. Always verify:
| Action | Verification |
|---|---|
| File edit | Re-read file, check syntax |
| Code change | Run tests, check build |
| API call | Check response status |
| Command exec | Check exit code, read output |
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.
- 6d ago First seen · 173 lines · 32 tokens per session scan A 0b3d7de30a6d
agentic-workflow is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 1,036 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-08-31.
Other skills, from other repositories
strands-review
Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
pr-writer
Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.
docs-audit
Assess a published or in-progress documentation page for quality, accuracy, and voice compliance. Use before rewriting a page, during periodic health checks, when community signals point to confusion, or when comparing against competitor docs. Also triggers on "audit this page", "assess the docs", "what's wrong with…
pre-push
Runs the local equivalent of the CI merge gate before you push. Detects which areas (Python, TypeScript, docs) your changes touch, auto-fixes what it can, then runs only those checks. Use when the user asks to run pre-push checks, get push-ready, verify changes before pushing or opening a PR, "make sure CI will pass"…
docs-planner
Identify documentation gaps and prioritize the docs backlog. Use when planning a docs improvement sprint, after signals surface repeated friction, when new SDK features ship without docs, or for periodic health assessment. Also triggers on "plan docs work", "what docs need writing", "prioritize the backlog", "docs…