Skip to content
Report library
Purpose / Other

Research Skill Security Audit

What the author says it does (original text)

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

Independent security check

No obvious risks found in this check

Files checked
2
Risks found
0
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.No risks found
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.No risks found
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.No risks found
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.No risks found

Inside this skill

0 instruction sections

This Skill delegates the research task to a background agent and directs it to verify the question against primary sources such as official documentation, source code, specifications, or first-party APIs.

View source
SKILL.md:6In the instructionsOpen original file
Spin up a **background agent** to do the research, so you keep working while it reads.Its job:1. Investigate the question against **primary sources** (official docs, source code, specs, first-party APIs), not a secondary write-up of them. Follow every claim back to the source that owns it.2. Write the findings to a single Markdown file, citing each claim's source.

The findings are written to one Markdown file in the repository. If the repository has no existing location convention, the background agent may choose a location it considers sensible and report it.

View source
SKILL.md:11In the instructionsOpen original file
1. Investigate the question against **primary sources** (official docs, source code, specs, first-party APIs), not a secondary write-up of them. Follow every claim back to the source that owns it.2. Write the findings to a single Markdown file, citing each claim's source.3. Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.
Start here · InstructionsSKILL.md
research

The instructions have no section headings. Supporting files and code excerpts are available below.

Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.
Files and check records2 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included
  • agents/openai.yamlFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions
  • agents/openai.yamlSupporting file
Lines read
17
File checksum (to compare versions)
173e3ff0e5714cfa165868ceb624bb739519556fb832b45a4ab6abe03ada51e1