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 markmhendrickson/neotoma --skill run-feature-workflowgit clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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/markmhendrickson/neotoma/run-feature-workflow)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/run-feature-workflow"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/run-feature-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/run-feature-workflow"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/run-feature-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 6 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00008 | $0.00732 |
| Opus 5.5 | $0.00003 | $0.00293 |
| Sonnet 5.5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
run-feature-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 1mo 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- run-feature-workflow — 92% identical, 10 lines differ
- run-feature-workflow — 92% identical, 7 lines differ
- run_feature_workflow — 80% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: run-feature-workflow description: Run feature workflow per foundation command. triggers:
- run feature workflow
- /run_feature_workflow
- run-feature-workflow
Run Feature Workflow
feature_id = {{input:feature_id}}
Configuration is read from foundation-config.yaml.
-
Load configuration:
- Read
foundation-config.yamlto get feature unit settings - Determine directory structure, manifest complexity, testing requirements
- Read
-
Read authoritative documents:
foundation/development/feature_unit_workflow.md(workflow context){configured_directory}/in_progress/{{input:feature_id}}/{{input:feature_id}}_spec.md(orcompleted/if completed){configured_directory}/in_progress/{{input:feature_id}}/manifest.yaml(orcompleted/if completed)foundation/development/templates/feature_unit_spec_template.md- Repository-specific execution instructions (if they exist)
- Repository-specific architecture/module documentation (based on spec)
-
Determine risk level:
- low → skip plan
- medium → produce brief structured plan
- high/critical → produce detailed plan and wait for user approval
-
Apply Feature Unit execution principles:
- Update spec/manifest if ambiguous
- Update code/tests/docs together
- Follow architectural invariants (from repo-specific docs)
- Preserve accessibility and i18n rules (if applicable)
-
Run tests (based on configuration):
- Unit tests (if
testing.require_unit_tests: true) - Integration tests (if
testing.require_integration_tests: true) - E2E tests (if
testing.require_e2e_tests: true) - Verify coverage meets configured targets
If any tests fail:
- Immediately invoke
Fix Feature Bugwith feature_id={{input:feature_id}} - Do NOT attempt to fix bugs inline
- Let the error protocol classify and correct
- After bugfix completes, re-run the test suite
- Only proceed to step 6 once all tests pass
- Unit tests (if
-
Apply error protocol (if repository has one) only if bugs were encountered and fixed via step 5.
-
Spec-to-Implementation Diff Checkpoint (CRITICAL):
Before producing the final summary:
- Compare the implemented code against the spec
- List any ways implementation intentionally diverged from spec (even if small)
- For each divergence:
- Either update the spec to reflect the change (if divergence is intentional and correct)
- Or mark the divergence as a bug to be fixed (if divergence is unintentional)
- Present this diff to the user:
- "Implementation vs Spec Diff: [list of divergences]"
- "For each divergence, should I update the spec or fix the implementation? (spec/implementation/list)"
- Do NOT proceed to final summary until spec and implementation are aligned (either by updating spec or fixing implementation)
-
Produce a final change summary:
- feature_id
- files changed
- risk
- error_class (if bugfix)
- tests run
- coverage achieved
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.
- 1mo ago First seen · 87 lines · 8 tokens per session scan A 3d9d7497bd4c
run-feature-workflow is a skill published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 732 once invoked, about $0.0000 per session on Opus 5.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
akf-trust-metadata
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.
bilibili_search
Search for videos on Bilibili using keyword queries generated from user interests.
bernstein-plan
Create and manage multi-step execution plans in Bernstein. Plans decompose complex goals into stages with dependencies. Use when the user wants to plan a complex feature, break down a large task, or review an execution plan before agents start working.
bernstein-run
Run a verified multi-agent goal with Bernstein. Use when a task is too large for a single agent session: Bernstein decomposes the goal into tasks, spawns CLI coding agents in parallel git worktrees, verifies their output, and merges results. Also use to check run status, costs, and to verify a finished run against its…
taste-explorer
A guided interview skill that asks focused questions to learn what a person likes and dislikes, then saves confirmed preferences as long-term memory.
bernstein-approve
Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.