agentleFS
hushh-labshushh-labs/hushh-research/.agents/skills/security-audit/SKILL.md

security-audit

Skill40 starsChanged 4 days agoApache-2.0View on GitHub

Use when the request is about IAM, consent, trust, ordinary vault encryption, failures decrypting PKM entries, PKM storage or persistence, encrypted PKM records, plaintext localStorage leaks, streaming safety, verification, or security audit workflows and no narrower specialist owns the change.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • +7 more from lilangMax
  • +1 more from nicepkg

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Avoid overlap with backend, repo-operations, and repo-context.

    line 12
  2. Distinctive:

    Keep trust-boundary docs aligned with code and verification changes.

    line 64
  3. Very specific:

    If the request begins as a cross-domain scan, start with repo-context.

    line 76

“Common” is measured: kept by at least 6 in 10 of the 174 edited versions of this file we could read. “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

Hussh Security Audit Skill

Purpose and Trigger

  • Primary scope: security-audit-intake
  • Trigger on IAM, consent, trust, ordinary vault encryption, PKM storage or manifest persistence, encrypted PKM records, plaintext localStorage leaks, verification, streaming, and audit-oriented requests where no narrower spoke owns the change.
  • Avoid overlap with backend, repo-operations, and repo-context.

Coverage and Ownership

  • Role: owner
  • Owner family: security-audit

Owned repo surfaces:

  1. docs/architecture/identity
  2. docs/development/streaming
  3. hushh-webapp/lib/consent
  4. hushh-webapp/lib/vault
  5. hushh-webapp/lib/pkm
  6. hushh-webapp/lib/personal-knowledge-model
  7. consent-protocol/hushh_mcp/consent
  8. consent-protocol/hushh_mcp/trust
  9. consent-protocol/hushh_mcp/vault

Non-owned surfaces:

  1. backend
  2. repo-operations
  3. docs-governance

Do Use

  1. Broad trust-boundary and audit intake before the correct spoke is clear.
  2. IAM, consent, vault, PKM, streaming-safety, and verification questions spanning docs and code.
  3. Owning ordinary vault/PKM persistence and choosing when work belongs to IAM/consent, reviewer/BYOK testing, PKM upgrade rehearsal, quality contracts, or streaming contracts.

Do Not Use

  1. Broad backend runtime work where trust is not the primary boundary.
  2. CI/deploy/env parity work that belongs to repo-operations.
  3. Broad repo mapping before the domain itself is known.

Read First

  1. docs/architecture/identity/README.md
  2. docs/development/streaming/README.md
  3. docs/development/repository-map.md
  4. docs/architecture/identity/agent-delegation-boundary.md
  5. consent-protocol/docs/reference/consent-protocol.md
  6. .agents/skills/security-audit/references/anti-rationalization.md
  7. consent-protocol/docs/reference/personal-knowledge-model.md
  8. consent-protocol/docs/reference/private-browser-runtime.md

Workflow

  1. Identify whether the real ownership surface is IAM/consent, vault/PKM, quality contracts, or streaming contracts.
  2. For ordinary vault/PKM changes, preserve memory-only keys, encrypted persistence, manifest authority, revision safety, and cache invalidation.
  3. Keep trust-boundary docs aligned with code and verification changes.
  4. Route general backend runtime work back to backend when trust is not the primary concern.
  5. For Computer Use, follow consent-protocol/docs/reference/private-browser-runtime.md: selected non-secret exports, manual login, encrypted opt-in sessions and generation-fenced Forget. No Secrets export, automatic credential injection or record-only cross-custody transfer is qualified by this pilot.
  6. For Shared Files, follow docs/operations/hosting/private-files-library.md: keep library keys in the unlocked browser, record storage incarnation before its first write, and retain erasure fences until the existing inventory has a qualified provider-absence receipt. A storage name or its present retention setting cannot establish historical cleanup. Shared upload session URIs are provider bearer credentials: encrypt their durable receipts through existing credential custody, bind them to the exact owner/library/operation/bucket, and require provider-terminal evidence before releasing a write fence. Never give Shared compute the browser library key.
  7. For account/cloud erasure, read docs/operations/identity/account-deletion-rollout.md and the provider's canonical lifecycle contract. Prove the installed schema accepts the actual producer receipt before irreversible work; rollback must serialize with active admissions. Resource ownership, writer drain, absence and retained-provider outcomes require separate evidence. Key destruction or an accepted DELETE cannot establish complete cleanup.

Handoff Rules

  1. Route consent scopes, actor model, and IAM/runtime gate work to iam-consent-governance.
  2. Route reviewer-account BYOK browser proof to reviewer-app-testing.
  3. Route zero-loss PKM upgrade acceptance to pkm-upgrade-rehearsal.
  4. Route cross-surface test policy to quality-contracts and streaming work to streaming-contracts.
  5. If the request begins as a cross-domain scan, start with repo-context.

Required Checks

./bin/hushh docs verify
cd consent-protocol && python3 -m pytest tests/quality -q

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.