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 bradtraversy/coding-with-ai-course-resources --skill featuregit clone --depth 1 https://github.com/bradtraversy/coding-with-ai-course-resourcesWrote 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/bradtraversy/coding-with-ai-course-resources/feature)<a href="https://agentmods.dev/skills/bradtraversy/coding-with-ai-course-resources/feature"><img src="https://agentmods.dev/badge/skills/bradtraversy/coding-with-ai-course-resources/feature.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.00014 | $0.00251 |
| Opus 5 | $0.00007 | $0.00125 |
| Sonnet 5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
feature 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 7d 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.
What it actually says
Feature Workflow
Manages the full lifecycle of a feature from spec to merge.
Working File
@context/current-feature.md
File Structure
current-feature.md has these sections:
# Current Feature- H1 heading with feature name when active## Status- Not Started | In Progress | Complete## Goals- Bullet points of what success looks like## Notes- Additional context, constraints, or details from spec## History- Completed features (append only)
Task
Execute the requested action: $ARGUMENTS
| Action | Description |
|---|---|
load |
Load a feature spec or inline description |
start |
Begin implementation, create branch |
review |
Check goals met, code quality |
explain |
Document what changed and why |
complete |
Commit, push, merge, reset |
See actions/ for detailed instructions.
If no action provided, explain the available options.
What ships with it
8 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.
- 7d ago First seen · 39 lines · 14 tokens per session scan A e78e8b6f653e
feature is a skill published in the GitHub repository bradtraversy/coding-with-ai-course-resources (319 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 251 once invoked, about $0.0001 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.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.