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 devantler-tech/agent-plugins --skill product-engineeringgit clone --depth 1 https://github.com/devantler-tech/agent-pluginsWrote 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/devantler-tech/agent-plugins/product-engineering)<a href="https://agentmods.dev/skills/devantler-tech/agent-plugins/product-engineering"><img src="https://agentmods.dev/badge/skills/devantler-tech/agent-plugins/product-engineering/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/devantler-tech/agent-plugins/product-engineering"><img src="https://agentmods.dev/badge/skills/devantler-tech/agent-plugins/product-engineering.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.00114 | $0.04842 |
| Opus 5.5 | $0.00046 | $0.01937 |
| Sonnet 5.5 | $0.00023 | $0.00968 |
| Haiku 4.5 | $0.00011 | $0.00484 |
Grade A, and why
product-engineering 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 yesterday.
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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product engineering — moving products forward
This is the advance half of an autonomous engineer's role: once nothing is on fire, proactively improve each product's direction, quality, and performance — not just its uptime. Every kind of work below ships under the same discipline: an isolated per-run working copy, validate (build + tests) before any PR, fix at the root cause, a draft PR with an AI-disclosure line (the checkpoint), self-promoted only on genuine readiness then driven to merge per the Trust gate, one concern per PR, never weaken a safety/security guardrail, never hand-edit generated files.
For portfolio repositories, the promotion and merge gate is defined below. For your own authorized contributions to a third-party project, follow the upstream contribution procedure for the separate Ready for Review handoff, private internal review and replies to received feedback. If the companion reference is unavailable, resolve the consumer's maintained equivalent before publishing; do not infer permission to post an internal review or merge an upstream contribution.
Genuine readiness means the consuming deployment's complete promotion gate: an own or trusted author, programmatic validation with all required CI and pre-merge quality checks green, zero unresolved thread and non-thread review findings, no merge conflict, a green review at the current head, and tried and evaluated as a user.
Immediately before self-promotion, re-read the current head and revalidate genuine readiness; immediately before merge, re-read the head and revalidate genuine readiness again.
This skill is authored against the consumer contract sections defined by the consuming deployment's
AGENTS.md (per the agentic-engineering plugin's parameterization contract): the Portfolio map
(which products exist, plus each product's ## Maintenance card — validate commands, labels,
protected/generated files, its feature-flag mechanism, and its roadmap home), the Trust gate (who
may be driven to merge and the per-repo merge mechanics), the Cadence (rotation frequencies for
strategy reviews and docs passes), Memory (where durable cross-run cursors live), and
Maintainer channels (how a human decision is actively reached). Where this skill says "per the
X section", the consuming repo supplies the concrete fact.
What ships with it
30 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.
- references/accountability-brief.md 13 KB
- references/accountability-infrastructure.json 5.5 KB
- references/accountability-library.json 6.1 KB
- references/accountability-product.json 5.3 KB
- references/evidence-bundle.md 13 KB
- references/evidence-example.json 6.3 KB
- references/partial-failure-regressions.md 4.7 KB
- references/shared-code.md 9.2 KB
- references/tool-maturation.md 14 KB
- references/upstream-release-review.md 8.7 KB
- references/value-pull.md 6.4 KB
- scripts/accountability-brief.jq 12 KB
- scripts/accountability-brief.sh 2.1 KB runs code
- scripts/accountability-brief.test.sh 1.0 KB runs code
- scripts/check-evidence.jq 19 KB
- scripts/check-evidence.sh 1.9 KB runs code
- scripts/check-evidence.test.sh 733 B runs code
- scripts/go-entrypoint_test.go 2.3 KB
- scripts/go-entrypoint.go 1.3 KB
- scripts/inspect-shell-ambiguity.test.sh 4.6 KB runs code
- scripts/inspect-shell-helpers.sh 11 KB runs code
- scripts/inspect-shell-helpers.test.sh 14 KB runs code
- scripts/inspect-shell-identity.test.sh 3.9 KB runs code
- scripts/inspect-shell-observation.test.sh 2.4 KB runs code
- scripts/inspect-shell-tree-integrity.test.sh 3.8 KB runs code
- scripts/select-work.jq 4.8 KB
- scripts/select-work.sh 1.3 KB runs code
- scripts/select-work.test.sh 5.0 KB runs code
- scripts/validate-json-unicode-escapes.sh 2.2 KB runs code
- scripts/validate-json-unicode-escapes.test.sh 868 B runs code
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.
- yesterday Changed · +38 lines · +7 tokens per session e08b81b937e8
- 7d ago Changed · +8 lines · +2 tokens per session e7eceedcbaf0
- 11d ago Changed 74b6486d0409
- 12d ago Changed 6049d5ca8bac
- 15d ago Changed · +58 lines · +7 tokens per session 7ec43b19b588
- 21d ago Changed · +13 lines 7d45ae68024b
- 1mo ago First seen · 183 lines · 98 tokens per session scan A 1bb3d30e4067
product-engineering is a skill published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 114 tokens to every session and 4,842 once invoked, about $0.0005 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
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
predictable-revenue
Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an outbound sales team", or "fill my pipeline". Also trigger when setting up a B2B…
team-topologies
Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or…
structured-plan-mode
This skill should be used when planning and tracking complex feature implementations that require systematic task decomposition. Use this skill to break down large features into manageable, well-documented tasks with clear dependencies, action items, and success criteria. The skill provides a structured template and…
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
run
Drive a GitHub issue — bare or tracked on a Project board — from triage to a merge-ready PR through a gated pipeline (design hardening, tests green, code-review clean), scaling the machinery to the task's tier and asking at most one batched question. Auto-links the issue to close on merge, advances the board card…