Borrowing it
Nothing to install: this file belongs to fqmyysjjd/agent-feed. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fqmyysjjd/agent-feed/main/.agents/skills/engineering-planning/SKILL.mdgit clone --depth 1 https://github.com/fqmyysjjd/agent-feedWrote 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/fqmyysjjd/agent-feed/engineering-planning)<a href="https://agentmods.dev/skills/fqmyysjjd/agent-feed/engineering-planning"><img src="https://agentmods.dev/badge/skills/fqmyysjjd/agent-feed/engineering-planning/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/fqmyysjjd/agent-feed/engineering-planning"><img src="https://agentmods.dev/badge/skills/fqmyysjjd/agent-feed/engineering-planning.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.00038 | $0.00664 |
| Opus 5.5 | $0.00015 | $0.00266 |
| Sonnet 5.5 | $0.00008 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
engineering-planning 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Planning
Required Use
Use this skill before any task that writes code, creates files, changes tests, moves project structure, introduces dependencies, or changes implementation behavior.
This skill exists to prevent "just add a file" work. The output must explain where the change belongs, what can be reused, and how the implementation will remain maintainable.
Required Reading
.agents/rules/outcome-boundary.md.agents/project/README.md.agents/project/project-structure.md.agents/project/architecture-boundaries.md.agents/domain/contracts.md- The nearest existing module, helper, adapter, command, test, or document that already owns related behavior.
Workflow
Before editing:
- Recover the current Task Brief and stop condition.
- Identify the owning layer: rule, skill, project constraint, domain knowledge, source module, script, adapter, test, or documentation.
- Search existing code, tests, helpers, templates, scripts, and docs for reusable behavior before creating anything new.
- Decide whether the change should extend an existing owner, create a small new owner, or avoid code changes entirely.
- Check whether the placement preserves project structure, source-of-truth ownership, public contracts, configuration boundaries, and generated-template boundaries.
- Choose the smallest write set that can satisfy the result without scattering related behavior.
- Decide the verification evidence before editing.
Engineering Planning Card
For non-trivial implementation or fix work, keep this compact card in working notes or the user-facing plan:
| Item | Decision |
| --- | --- |
| Owner | Existing module/file/layer that should own the change |
| Reuse | Existing code, helper, pattern, test, or doc to reuse |
| Placement | Where the change belongs and why |
| Write set | Files/directories expected to change |
| Boundary | Public contract, config, template, adapter, security, or project boundary to preserve |
| Verification | Tests/checks that prove the result |
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 · 71 lines · 38 tokens per session scan A 657a3952698b
engineering-planning is a skill published in the GitHub repository fqmyysjjd/agent-feed (4 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 664 once invoked, about $0.0002 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-31.
Other skills, from other repositories
import
Import a tasks.md into the coco tracker as an epic with dependencies, and create matching issues in the configured issue tracker.
agent-engineering
Decision framework for which agent-engineering mechanism, if any, fits a workflow problem: durable rule, skill, hard constraint, verification, eval, eval harness, feature map, observability, or increased automation/trust. Use whenever agents keep breaking something, a change isn't trusted yet, it's unclear if Claude…
init
Set up project docs, coding standards, architecture, and ADR scaffolding. Works for greenfield and existing repos.
dxkit-allowlist
Manage the dxkit allowlist over its whole lifecycle — list, inspect, audit (including orphaned entries after a re-baseline), bulk-defer newly published dep-vuln advisories, remove stale entries, prune expired ones, and export Snyk-originated suppressions to a .snyk policy. Use when the user says "review our…
dxkit-checks
Declare and operate custom repo invariants as first-class guardrail gates — a project rule (a "no imports from X" check, an architecture script, a license audit) or the built-in per-language lint gate. Use when the user says "make our lint errors block the PR", "gate our custom check", "add a repo rule to the…
dxkit-update
Walk the customer through upgrading dxkit to a newer version safely. Use when the user asks "update dxkit", "upgrade to latest", "what's new in dxkit", "is there a new dxkit version", "should I upgrade dxkit", or anything about moving an existing dxkit install forward. Reads version delta + changelog + recommended…