CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

30.8 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 1 flagged

Securityscore 88 · 1 finding

MEDIUM"Never tell the user" non-disclosure imperative in the skillSS-SKILL-INJECT-IMPERATIVE-01 · Prompt injection · skills/issue-driven-workflow/assets/_template.md

MEDIUM — it fires on intent; whether the agent honors the non-disclosure imperative depends on the host model.

Why it matters

A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.

The exact value spotted

excerptskills/issue-driven-workflow/assets/_template.md· markdown

40## Issue CSV

41- Path: issues/<YYYY-MM-DD_HH-mm-ss>-<slug>.csv

42- Must share the same timestamp/slug as this plan.

43- Column spec: `references/issue-csv-spec.md`

Occurrences

1 occurrence · at L42

How to fix

Remove the non-disclosure imperative, or rescope it so it limits output format, not honesty to the user.

Delete any "never reveal / never tell the user" line aimed at the model's own behavior.
Keep legitimate confidentiality rules about external data (e.g. "do not echo API keys"), which are user-protective, not user-deceiving.

Framework references

OWASPLLM01 ATLASAML.T0051

Trace & refs

ruleSS-SKILL-INJECT-IMPERATIVE-01sha2569063a541ef5ddef1…rubric 365aacaView on GitHub

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/issue-driven-workflow/SKILL.md · 1 file

skills/issue-driven-workflow/SKILL.md3.9 KB · Markdown

name: issue-driven-workflow

description: Break down complex tasks into a structured plan and trackable Issue CSV, then execute autonomously. Use when a task has multiple steps, needs research before starting, requires status tracking, or benefits from a structured breakdown before execution.

metadata:

short-description: Plan → Issue CSV → autonomous execution

Issue-Driven Workflow

Philosophy

The plan and Issue CSV are a work amplifier. Front-load the thinking so the agent has a full plate of actionable work to execute autonomously — more rows means more useful work per run.

Planning (interactive) — search the web, read docs, ask questions, gather context. A thorough plan means more work the agent can do without stopping.
Execution (autonomous) — be proactive, not passive. Work through the CSV end-to-end. Maximize useful work per run — don't wait for permission on routine decisions.

The quality bar: every CSV row should be completable, testable, and markable DONE without further clarification.

E2E loop

plan → issues → implement → test → review

Planning (interactive)

Restate the task and assumptions.
Gather context — search the web, read project files, inspect dependencies. Make every plan section concrete, not aspirational.
Ask up to 2 clarification questions if unclear, then proceed with stated assumptions.
Draft the plan in chat using assets/_template.md. Choose complexity (simple|medium|complex).
Ask: "Reply CONFIRM to write the plan file."
On confirmation:

   python3 .codex/skills/issue-driven-workflow/scripts/create_plan.py \
     --task "<title>" --complexity <simple|medium|complex>

Do not edit code while planning.

Creating the CSV (interactive)

Generate after the plan is approved.
Break the plan into granular, independently actionable rows.
Fill all required columns — see references/issue-csv-spec.md.
Order by dependency chain. Set Dependencies so execution order is unambiguous.
Validate:

   python3 .codex/skills/issue-driven-workflow/scripts/validate_issues_csv.py <issues.csv>

Executing the CSV (autonomous)

The CSV is your execution state. Read it to know where you are, update it as you work, keep driving forward.

Read the CSV. Find the next TODO row in dependency order.
Set Dev_Status = DOING. Start working.
Complete the row — search, read, write, test, whatever it requires.
When Acceptance is met and Test_Method passes, set Dev_Status = DONE.
Self-review. Mark Review1_Status = DONE.
Immediately move to the next row. Read the CSV again, pick the next TODO, keep going.
After all rows are DONE, regression check. Mark Regression_Status = DONE per row.
Report progress briefly as you complete rows.
Only stop for genuinely blocking unknowns that affect correctness, safety, or irreversible actions.

If a row is too large, split it. If a row fails, fix it or flag it. If in a git repo, commit at natural boundaries. Edit the CSV directly — re-validate after edits.

Scripts

Script	Purpose
`create_plan.py`	Create a plan file with YAML frontmatter under `plan/`
`list_plans.py`	List existing plans (supports `--query`, `--json`)
`validate_issues_csv.py`	Validate Issue CSV schema and status values

Run with --help first. Scripts live in scripts/ relative to this skill.

Naming

Plans: plan/YYYY-MM-DD_HH-mm-ss-<slug>.md — Issue CSVs: issues/YYYY-MM-DD_HH-mm-ss-<slug>.csv — same timestamp/slug.

References

Issue CSV spec — read when creating or validating CSVs
Testing policy — read when filling `Test_Method`
Plan template — structure with complexity tiers
CSV template — example rows with plan-to-CSV mapping

issue-driven-workflow— agent skill

Is issue-driven-workflow safe to install?

Issue-Driven Workflow

Philosophy

E2E loop

Planning (interactive)

Creating the CSV (interactive)

Executing the CSV (autonomous)

Scripts

Naming

References

Audit the pieces. Scan the whole. Decide.