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 bdfinst/agentic-dev-team --skill issues-from-assessmentgit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWrote 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/bdfinst/agentic-dev-team/issues-from-assessment)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/issues-from-assessment"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/issues-from-assessment/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/bdfinst/agentic-dev-team/issues-from-assessment"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/issues-from-assessment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 105 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00138 | $0.03260 |
| Opus 5.5 | $0.00055 | $0.01304 |
| Sonnet 5.5 | $0.00028 | $0.00652 |
| Haiku 4.5 | $0.00014 | $0.00326 |
Grade A, and why
issues-from-assessment 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 1mo 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issues from Assessment
Role: worker. Converts the assessment produced by /cd-test-architecture into the tracker artifacts the calling test-improvement workflow expects (Feature/Epic + Phase-tagged Stories + Tasks with predecessor links), or — when no tracker CLI is available — into local plan files with the same structure. Lifts the preview-then-confirm + gh issue create patterns from /issues-from-plan.
You have been invoked with the /issues-from-assessment command.
Parse Arguments
Arguments: $ARGUMENTS
- Positional:
<assessment-path>— the file/cd-test-architecturewrote (.dev-team-reports/cd-test-architecture-<app>.md). --parent <issue-url>— parent issue / Feature / Epic URL. Empty or omitted → local-files mode.--repo-slug <slug>— slug used for the.claude/memory/<workflow>/<slug>/namespace. Defaults to the assessment file's<app>token.--workflow <name>— the workflow namespace under.claude/memory/and.claude/plans/, and the leading tracker-label token. Defaults totest-improve. Callers pass their own namespace so parallel runs stay quarantined.--refactor-mode <no-refactor|refactor-allowed>— optional; the caller's Phase-0 refactor choice. Defaults torefactor-allowed(unchanged behavior) when omitted. Whenno-refactor, the Phase-5[Refactor-for-testability]work is emitted as out-of-scope / skipped-in-no-refactor plan entries — informational context only, never actionable Stories — so the written plan shows the coverage/behavior left on the table without offering refactor work this run will not do.--dry-run— print the preview list and exit without creating anything.
If <assessment-path> is absent or the file is missing, ask the operator to point at one.
Path + label templates. Every filesystem path and every operator-visible tracker label in the Steps below carries <workflow> as a placeholder — the skill interpolates the resolved --workflow value at run time. No literal workflow name appears in a path or label string.
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.
- 1mo ago First seen · 217 lines · 138 tokens per session scan A ed728b9833af
issues-from-assessment is a skill published in the GitHub repository bdfinst/agentic-dev-team (297 stars, last pushed today), licensed MIT. It adds 138 tokens to every session and 3,260 once invoked, about $0.0006 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-03.
Other skills, from other repositories
team-qa
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
test-result-feedback
Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.