agentics-beyond-code: Skill for Claude Code

.github/skills/productboard-agent-builder/SKILL.md

productboard-agent-builder is a skill for Claude Code, Codex from chrizbo/agentics-beyond-code. It costs 98 tokens per session (2,297 once invoked), scanned A, original, MIT.

A workflow that turns a product team's discovery, feedback, strategy, or planning process into instructions for Productboard Spark, Productboard's agent workspace.

In plain words
What is it for?
Use it to adapt repository workflows into Spark skills or instructions for product work.
Why use it?
It helps preserve the original process and its evidence when moving that process into Productboard, instead of rewriting it from memory.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

This is chrizbo/agentics-beyond-code's own configuration. It tells Claude Code and Codex how to work on agentics-beyond-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentics-beyond-code configures →

Reuse

Borrowing it

Nothing to install: this file belongs to chrizbo/agentics-beyond-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/chrizbo/agentics-beyond-code/main/.github/skills/productboard-agent-builder/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/chrizbo/agentics-beyond-code

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for productboard-agent-builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/chrizbo/agentics-beyond-code/productboard-agent-builder/github.svg)](https://agentmods.dev/skills/chrizbo/agentics-beyond-code/productboard-agent-builder)
Your own site
<a href="https://agentmods.dev/skills/chrizbo/agentics-beyond-code/productboard-agent-builder"><img src="https://agentmods.dev/badge/skills/chrizbo/agentics-beyond-code/productboard-agent-builder/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.

agentmods 80×15 button for productboard-agent-builder

Your own site · 80×15
<a href="https://agentmods.dev/skills/chrizbo/agentics-beyond-code/productboard-agent-builder"><img src="https://agentmods.dev/badge/skills/chrizbo/agentics-beyond-code/productboard-agent-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,297 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00098 $0.02297
Opus 5.5 $0.00039 $0.00919
Sonnet 5.5 $0.00020 $0.00459
Haiku 4.5 $0.00010 $0.00230

Measured 18d ago against content hash 7cada54c98cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

productboard-agent-builder 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 18d 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.

.github/skills/productboard-agent-builder/SKILL.md · 197 lines

How it starts

The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Productboard Agent Builder

Turn a selected workflow into instructions a product team can use in Productboard. Follow the Claude-native builder's source-first approach: preserve the workflow's purpose, evidence, readable artifacts, and human interpretation points while adapting its execution to the chosen product surface.

Choose the target and source

Default to Productboard Spark custom skills for reusable native instructions. If the user means an external agent connected to Productboard, respect that choice and identify its runtime separately. Productboard's outbound MCP server and connectors used inside Spark are different access paths; neither proves the other's capabilities. Do not switch to Claude or GitHub execution just because those tools are available locally.

For a port, locate and read the actual selected .github/workflows/*.md or .yml source. Read referenced policies, input schemas, and scripts when they affect behavior. Use the workflow name and description to narrow the search; do not load the entire workflow catalog. Treat generated .lock.yml files as implementation evidence when needed, not the authoring source. Record which source and revision you actually inspected, including local modifications.

For a new process, start from an agentic-workflow-planner design when one exists, or run its Design mode (../agentic-workflow-planner/references/design.md) briefly. Then establish the Spark-specific details: intended artifact, evidence sources, scope, reviewer, destination, and invocation. Reuse relevant repository patterns without claiming the new design is an exact port. Preserve the user's requested skill name exactly; otherwise choose a plain descriptive name without repository prefixes or test suffixes unless requested. Ask only for missing decisions that change the output; use clearly marked placeholders for target-specific values.

Installed package source access

In this repository, resolve repository paths from its root. In the generated plugin, the package root is three directories above this file. Read the package's docs/source-access.md before accessing workflows outside this skill: they are not bundled. Use a supplied checkout (the working directory when it is this repository, or a path the user gives) or the recorded source index to fetch the selected files. Never search the file system for a checkout; broad scans trigger operating-system privacy prompts. Name the retrieved revision rather than calling it current upstream. If neither source is accessible, request the relevant files and offer only a clearly labeled new design meanwhile. Resolve this skill's references relative to this folder; write user deliverables in their chosen workspace.

Read the full file on GitHub · 197 lines

Files

What ships with it

4 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.

Changes

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.

  1. 18d ago Changed · +16 lines 7cada54c98cc
  2. 25d ago First seen · 181 lines · 98 tokens per session scan A 137c5eb82e91

Subscribe to this mod's changes

productboard-agent-builder is a skill published in the GitHub repository chrizbo/agentics-beyond-code (34 stars, last pushed 4d ago), licensed MIT. It adds 98 tokens to every session and 2,297 once invoked, about $0.0004 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-09-30.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens