agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/program-memory/SKILL.md

program-memory

Skill1 starsChanged 3 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After each run: import-run to ingest findings and facts.

    line 15
  2. Very specific:

    Before planning: export-planner-hints for ranking signals.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Program Memory

Overview

Persist target-specific knowledge across engagements. Track accepted/rejected findings, false-positive patterns, rate limits, auth behavior, object ID formats, WAF quirks, and technology profiles. Feed learning back into planner rankings.

Quick Reference

  • Skill: program-memory
  • Version: 1.0.0
  • Bounded Context: ProgramMemoryContext
  • Required tools: python3, jq
  • Risk tier: passive

Workflow Selection

  • New program: init-memory to create the memory store.
  • After each run: import-run to ingest findings and facts.
  • Before planning: export-planner-hints for ranking signals.
  • Review: record-fact or record-false-positive for manual notes.

Available Workflows

WorkflowPurpose
init-memoryCreate program memory store for the current program.
import-runIngest findings, facts, and patterns from current run.
record-factAdd a manual fact about the program.
record-false-positiveRecord a confirmed false-positive pattern.
record-findingRecord a submitted/finalized finding.
summarize-memoryProduce human-readable memory summary.
export-planner-hintsExport planner-weighting hints from accumulated memory.

Redaction and Storage Policy

Program memory is local-only: the SQLite store (.bb/memory.sqlite) and all summaries live under .bb/ / $OUTDIR and are never committed (keep them in .gitignore). Before any fact is persisted, secrets, tokens, cookies, and auth headers must be redacted; the export-safe workflow enforces this redaction so only report-safe, sanitized facts ever leave the store.

Evidence Required

  • Program facts with source attribution and confidence.
  • False-positive patterns with example request/response pairs.
  • Finding history with Bugcrowd/HackerOne verdicts.

References

  • Bugcrowd VRT 1.18
  • OWASP WSTG-INFO-01 (Reconnaissance)
  • OWASP ASVS V1 (Architecture)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.