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 Viniciuscarvalho/Feature-marker --skill codexgit clone --depth 1 https://github.com/Viniciuscarvalho/Feature-markerWrote 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/viniciuscarvalho/feature-marker/codex)<a href="https://agentmods.dev/skills/viniciuscarvalho/feature-marker/codex"><img src="https://agentmods.dev/badge/skills/viniciuscarvalho/feature-marker/codex/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/viniciuscarvalho/feature-marker/codex"><img src="https://agentmods.dev/badge/skills/viniciuscarvalho/feature-marker/codex.svg" alt="Reviewed on agentmods" width="80" 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.00305 |
| Opus 5.5 | $0.00013 | $0.00122 |
| Sonnet 5.5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
feature-marker 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 2mo 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
1 near-identical copy found in the catalogue:
- feature-marker — 89% identical, 8 lines differ
What it actually says
feature-marker for Codex
Use this skill from inside Codex prompts:
Use feature-marker to implement billing-observability.
Run the complete flow by default:
- Create or reuse
tasks/{slug}/prd.md,tasks/{slug}/techspec.md, andtasks/{slug}/tasks.md. - Use the bundled templates in
templates/for PRD, TechSpec, and Tasks; fill{slug}and{feature_title}and leave no unresolved placeholders. - Create or require a feature branch before implementation.
- Use a git worktree only when the checkout is dirty or the user asks.
- Run an implementation grill pass before coding to find artifact, task, test, risk, and handoff gaps.
- Resolve grill findings in the artifacts, asking the user only when a finding changes scope or requires a product decision.
- Stop only for true ambiguity, unrelated dirty work, or blocked verification.
- Run verification, commit locally, and print exact push/PR handoff commands.
- Do not push, open a PR, create checkpoint JSON, or use an interactive menu.
spec-driven and ralph-loop are out of scope for this skill-first v1 unless
they are rebuilt as explicit skill instructions.
What ships with it
1 file 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.
- 2mo ago First seen · 34 lines · 32 tokens per session scan A 1a4525a06f33
feature-marker is a skill published in the GitHub repository Viniciuscarvalho/Feature-marker (11 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 305 once invoked, about $0.0001 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
openspec-bulk-archive-change
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
openspec-archive-change
Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".
patent-docket
A workflow coordinator for patent case files, from an inventor's technical disclosure to patent application documents. A patent docket is the tracked record of a patent matter, including its stage, questions, drafts, and handoffs.
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.
ledger-tasks-yylo
Comprehensive guide for using YYLO Ledger task management without bypassing controller routing, lifecycle state, or mutation receipts. Covers task commands, dependency management, best practices, and workflow patterns. Use when you need to interact with the YYLO Ledger board.
tasks
Work on or manage records in BB Tasks, including task keys such as ABC-12.