Skip to content
cccskills
FreePublished on GitHub

variant-discovery

Systematically search an authorized codebase or protocol for additional manifestations of a confirmed root cause while preventing duplicate inflation and preserving independent verification requirements.

The English summary is being prepared. Showing the original description.

Sekolah76/syadagentic92 stars(GitHub 92 + cccskills 0)

Run score Not tested

See how to install

Files included (3)

  • SKILL.md2.8 KB
  • references/variant-patterns.md929 B
  • templates/variant-discovery.yaml706 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Variant Discovery

Mission

Given a confirmed or high-confidence root-cause fingerprint, identify semantically related manifestations across the target. Discover breadth without assuming every syntactic match is vulnerable.

Required inputs

  • Root-cause fingerprint.
  • Confirmed vulnerable example.
  • Relevant architecture and attack-surface map.
  • Scope and repository revision.

Search strategy

1. Extract semantic signature

Capture:

  • violated invariant;
  • missing/incorrect operation;
  • attacker-controlled dimension;
  • vulnerable data type or state transition;
  • source and sink relationship;
  • required context/configuration;
  • remediation pattern.

2. Generate search families

Use multiple families:

  • direct symbol/helper usage;
  • sibling handlers and implementations;
  • duplicated code and generated bindings;
  • alternate parsers/serializers;
  • inverse operations such as mint/burn, lock/unlock, encode/decode;
  • lifecycle variants: create/update/delete, startup/runtime/restart/replay;
  • boundary variants: single-tenant/cross-tenant, local/remote, on-chain/off-chain;
  • data-shape variants: signed/unsigned, truncation, zero/max, empty/duplicate, canonical/noncanonical;
  • protocol phase variants: epoch/round/view, source/destination chain, pre/post finality.

3. Screen candidates

For each match verify:

  • attacker reachability;
  • equivalent missing invariant;
  • equivalent attacker control;
  • relevant production path;
  • absence of compensating guards;
  • observable primitive;
  • same or different remediation boundary.

4. Classify

  • CONFIRMED_VARIANT: independently reproduced.
  • LIKELY_VARIANT: equivalent path and invariant, reproduction pending.
  • STRUCTURAL_MATCH_ONLY: syntax/pattern match without exploitability proof.
  • NOT_A_VARIANT: different root cause or guard prevents issue.
  • SAME_MANIFESTATION: duplicate path to the already known instance.

5. Avoid report inflation

Multiple variants are not automatically multiple bounty reports. Send them to Root Cause Analyzer for clustering. Prefer one report that demonstrates systemic breadth unless separate security boundaries, patches, or impacts justify separation.

6. Stop conditions

Stop expanding when:

  • searches saturate with no new semantic matches;
  • remaining matches are test/dead/generated code only;
  • all uses are guarded;
  • scope boundary is reached;
  • evidence quality declines into speculation.

Special domain patterns

Use references/variant-patterns.md.

Output

Use templates/variant-discovery.yaml. Every confirmed or likely variant must include a verifier test specification.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Provide comprehensive techniques for testing REST, SOAP, and GraphQL APIs during bug bounty hunting and penetration testing engagements. Covers vulnerability discovery, authentication bypass, IDOR exploitation, and API-specific attack vectors.

The English summary is being prepared. Showing the original description.

Sekolah76/syadagentic92Updated Aug 27, 2026

Web2 attack chain plugin — apply Web2 trust boundaries and composition rules on top of attack-chaining-core for authorized testing of web apps, APIs, identity, cloud, and internal services.

The English summary is being prepared. Showing the original description.

Sekolah76/syadagentic92Updated Aug 27, 2026

Web3 attack chain plugin — apply Web3 state, economic, cryptographic, and consensus semantics on top of attack-chaining-core for authorized testing of smart contracts, DeFi, bridges, wallets, and validators.

The English summary is being prepared. Showing the original description.

Sekolah76/syadagentic92Updated Aug 27, 2026

Domain-neutral attack chain analysis — determine whether independently identified security primitives compose into a realistic, authorized, evidence-backed attack path with greater impact.

The English summary is being prepared. Showing the original description.

Sekolah76/syadagentic92Updated Aug 27, 2026

Build an evidence-backed map of externally and internally reachable attack surfaces, trust boundaries, privileged transitions, security assets, and high-value audit targets before vulnerability hunting.

The English summary is being prepared. Showing the original description.

Sekolah76/syadagentic92Updated Aug 27, 2026

Use at the START of any bug bounty hunting session, when switching targets, or when feeling lost about what to do next. Master orchestrator that combines the 5-phase non-linear hunting workflow with the critical thinking framework (developer psychology, anomaly detection, What-If experiments). Routes to all other skills based on current hunting phase. Also use when asking "what should I do next" or "where am I in the process."

The English summary is being prepared. Showing the original description.

Sekolah76/syadagentic92Updated Aug 27, 2026

See all skills by Sekolah76

Report a problem with this skill