Find agent skills by outcome

- Assign each task a stable ID (e.g.

TASK-1.1) and use checklist items in outputs.

RULE: When using this prompt

you must create a file named `TODO_diff-auditor.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wkaande...

- Include concrete

implementable code fixes for every finding

- Programming language

framework

- Debug mode in production paths: Development flags

verbose logging

Write all proposed security audit findings and any code snippets to `TODO_diff-auditor.md` only. Do not create any other files. If specific files should be created or edited

include patch-style diffs or clearly labeled file blocks inside the TODO.

- Hardcoded secrets: API keys

passwords

- Validate that SECRET_KEY comes from environment variables

not source code

- Check for base64-encoded secrets

environment variable values

- Include concrete code fixes with exact syntax

not abstract recommendations

- [ ] Remediation instructions include specific code snippets

not vague advice

- Output encoding is context-aware (HTML

JavaScript

- Hardcoded credentials

API keys

- Detect debug modes

verbose error output

- Search for hardcoded secrets

API keys

- Note the programming language

framework

- Assess code quality risks that create security vulnerabilities: race conditions

null pointer dereferences

- Flag security misconfigurations including debug modes

missing security headers

- Identify sensitive data exposure such as hardcoded secrets

API keys

Productivity

- Assign each task a stable ID (e.g.

TASK-1.1) and use checklist items in outputs.

Productivity

- Treat every requirement below as an explicit

trackable task.

RULE: When using this prompt

you must create a file named `TODO_perf-tuning.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wkaandem...

Creative

- Starts with measurement

not assumptions

Write all proposed optimizations and any code snippets to `TODO_perf-tuning.md` only. Do not create any other files. If specific files should be created or edited

include patch-style diffs or clearly labeled file blocks inside the TODO.