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/am-space/own-planner/develop-ownplanner-featurenpx skills add am-space/own-planner --skill develop-ownplanner-featuregit clone --depth 1 https://github.com/am-space/own-plannerWrote 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/am-space/own-planner/develop-ownplanner-feature)<a href="https://agentmods.dev/skills/am-space/own-planner/develop-ownplanner-feature"><img src="https://agentmods.dev/badge/skills/am-space/own-planner/develop-ownplanner-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 | $0.00123 | $0.01573 |
| Opus 5 | $0.00062 | $0.00787 |
| Sonnet 5 | $0.00025 | $0.00315 |
| Haiku 4.5 | $0.00012 | $0.00157 |
Grade A, and why
develop-ownplanner-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 5d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop an OwnPlanner Feature
Execute an issue-driven feature as a traceable sequence: intake, plan, plan review, implementation, verification, and handoff. Touch only the layers required by the behavior.
Treat the Issue as the Contract
- Treat the repository issue as the canonical record of the outcome, acceptance criteria, discussion, and implementation history.
- Treat GitHub Project fields such as Status, Priority, Size, and Iteration as planning context, not as a duplicate feature specification.
- Follow parent issues, sub-issues, dependencies, linked plans, ADRs, and prior pull requests when they affect scope.
- Use a Project draft only for discovery. Ask the user to convert it to a repository issue before creating a branch or pull request that must close it.
- If given a direct request instead of an issue, form a temporary feature contract from the request. Do not create an issue or modify GitHub state unless the user authorizes it.
Follow the Required Workflow
1. Read the Issue and Repository State
- Read the root and applicable scoped
AGENTS.mdfiles. - Inspect the worktree, current branch, and relationship to
master. Preserve unrelated user changes. - Read the issue, including comments and relationships. Prefer
gh issue view <number-or-url> --commentswhen GitHub CLI access is available. - Extract:
- user-visible outcome;
- acceptance criteria and edge cases;
- explicit exclusions;
- priority and planning context;
- dependencies and blockers;
- unresolved product or technical decisions.
- Decide whether the issue is ready. Record harmless assumptions. Pause for user direction only when ambiguity would materially change behavior, public contracts, stored data, security, or scope.
Do not silently edit the issue, Project fields, relationships, or comments. External planning changes require authorization.
2. Explore Existing Patterns
- Find the closest implemented feature and its tests.
- Inspect relevant reference docs and ADRs before proposing a new abstraction.
- Reuse existing naming, folders, DTOs, errors, authentication, tenant resolution, and test patterns.
- Read references/feature-paths.md for every potentially affected delivery or persistence path.
What ships with it
3 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.
- 5d ago First seen · 122 lines · 123 tokens per session scan A 60260c7bff4c
develop-ownplanner-feature is a skill published in the GitHub repository am-space/own-planner (2 stars, last pushed 6d ago), licensed MIT. It adds 123 tokens to every session and 1,573 once invoked, about $0.0006 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
api-validator
Scan Bifrost HTTP controllers/handlers/integrations and validate OpenAPI API coverage, route methods/paths, parameters, request/response docs, and auth/security information. Use when asked to audit missing or incorrect APIs, compare controllers against docs/openapi, validate auth information, or fix API documentation…
docs-writer
Write, update, and review Mintlify MDX documentation for Bifrost features. Explores the full codebase (UI, Go backend, config schema), validates config.json examples, places screenshot placeholders, and presents outlines for approval before writing. Invoked with /docs-writer , /docs-writer update , or /docs-writer…
e2e-test
Skill "e2e-test" from maximhq/bifrost, covering playwright e2e testing, usage, workflow overview, auto-update workflow (sync mode) and step 0: detect what changed.
investigate-issue
Investigate a GitHub issue by fetching details, analyzing the codebase, researching documentation, and presenting an actionable implementation plan with test guidance. Use when asked to investigate, analyze, triage, or plan work for a GitHub issue. Invoked with /investigate-issue or /investigate-issue (prompts for ID).
changelog-writer
Write changelogs for Bifrost releases. Reads git history, bumps module versions following the core→framework→plugins→transport hierarchy, writes transports/changelog.md (enterprise-style) and per-module changelog.md files, and updates version files. Invoked with /changelog-writer or /changelog-writer .
resolve-pr-comments-stack
Resolve unresolved PR review comments across an entire Graphite (gt) stack of many PRs, bottom-up, in one working directory. Use when asked to "go through this stack and resolve comments", "clean up review comments across the whole stack", or given a list/range of PR numbers that form (or partially form) a gt stack.…