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

auth

Skill1 starsChanged 3 months agoMITView on GitHub

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ci-cd, error-handling 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.
  • JohnJBorenSkill

    ci-cd

    CI/CD pipeline design, GitHub Actions, testing automation, and deployment strategies

    Also in 4 projects that use this

  • MicrosoftSkill

    error-handling

    统一错误处理系统。在添加 API 端点、修改错误处理、添加前端 API 调用、编写错误相关测试时使用。

    Also in 5 projects that use this

  • diego-tobalinaSkill

    logging

    Logging best practices for Java (SLF4J/Logback) and Node.js (Winston/Pino). Use for structured logging, log levels, and avoiding sensitive data exposure.

    Also in 3 projects that use this

  • SentrySkill

    github-issues

    Create, update, comment on, label, and inspect GitHub issues with concise, evidence-backed content. Use when users ask to open, edit, view, close, reopen, or triage GitHub issues — including tracking bugs, features, or tasks. Prefer this skill over generic repository tools for issue operations; do not use for pull requests, branches, pushes, or PR creation order questions.

    Also in 3 projects that use this

  • wrsmith108Skill

    docker

    Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.

    Also in 3 projects that use this

  • SentrySkill

    ui-design

    Also in 3 projects that use this

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 19 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:

    Start with jwt-analysis unless prior evidence points to a more specific workflow.

    line 16
  2. Very specific:

    Follow each workflow next mapping in skill.yaml after reviewing generated findings.

    line 17
  3. Distinctive:

    If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 19 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

Auth

Overview

Authentication and authorization testing — JWT attacks, OAuth 2.0, SAML, session management, 2FA bypass, password reset, IDOR, privilege escalation

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

Quick Reference

  • Skill: auth
  • Severity range: medium, high, critical
  • Required tools: curl, ffuf, python3, jwt_tool, openssl, jq, hashcat
  • Expected input files: auth_pages.txt, all_urls.txt, js_files.txt
  • Scope check: confirm authorization before running intrusive or authenticated testing.

Workflow Selection

  • Start with jwt-analysis unless prior evidence points to a more specific workflow.
  • Follow each workflow next mapping in skill.yaml after reviewing generated findings.
  • If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.
  • Runbooks: use runbooks/ and select the closest phase runbook when workflow names do not map 1:1.

Available Workflows

WorkflowPurposeScript pathsPrimary outputsEvidence
jwt-analysisDecode a supplied JWT and optionally generate safe attack variants..claude/skills/auth/scripts/jwt_analyzer.py$OUTDIR/auth/jwt/findings.jsonl$OUTDIR/auth/jwt/evidence/
jwt-attack-matrixTest JWT none, HS/RS confusion, and replay against an optional target URL..claude/skills/auth/scripts/jwt_attack_matrix.py$OUTDIR/auth/jwt/attack_findings.jsonl$OUTDIR/auth/jwt/evidence/
oauth-redirectsTest OAuth authorization redirect URI bypass variants..claude/skills/auth/scripts/oauth_redirect_matrix.py$OUTDIR/auth/oauth/findings.jsonl$OUTDIR/auth/oauth/evidence/
mfa-flowProbe MFA-protected access, OTP reuse, and resend rate limiting..claude/skills/auth/scripts/mfa_flow_tester.py$OUTDIR/auth/mfa/findings.jsonl$OUTDIR/auth/mfa/evidence/
auth-raceSend concurrent requests to a selected auth-sensitive endpoint..claude/skills/auth/scripts/auth_race_tester.py$OUTDIR/auth/race/results.json$OUTDIR/auth/race/evidence/

Evidence Required

  • Save raw request and response data for each confirmed finding.
  • Include timestamps, affected target, exact workflow name, tool versions, and reproduction steps.
  • Store screenshots or terminal captures in the workflow evidence directory when the workflow defines one.
  • Evidence templates from skill.yaml:
  • jwt_forge: Forged JWT token + successful access response
  • oauth_bypass: Redirect URI bypass request/response with stolen code
  • idor_data: Response body showing another user's private data

References

  • Source of truth: skill.yaml
  • Runbooks: runbooks/
  • OWASP WSTG: WSTG-ATHN-01, WSTG-ATHN-02, WSTG-ATHN-03, WSTG-ATHN-04, WSTG-ATHN-05, WSTG-ATHN-06, WSTG-ATHN-07, WSTG-ATHN-08, WSTG-ATHN-09, WSTG-ATHN-10, WSTG-ATHZ-01, WSTG-ATHZ-02, WSTG-ATHZ-03, WSTG-ATHZ-04
  • OWASP API Top 10: API1:2023, API2:2023, API3:2023, API5:2023

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.