AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Tn Nemesis Scan

skill-grantkee-claude-extensions-tn-nemesis-scan · by grantkee

Deep combined audit using iterative Feynman + State Inconsistency analysis across 8 phases with specialized agents. Language-agnostic. Dynamically discovers domain-specific patterns via Phase -1 before the main pipeline. Spawns nemesis-orchestrator which coordinates domain discovery, recon, mapping, interrogation, state checking, feedback loop, journey tracing, verification, and reporting. Trigge…

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-grantkee-claude-extensions-tn-nemesis-scan

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-grantkee-claude-extensions-tn-nemesis-scan)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Tn Nemesis Scan? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Nemesis Scan

Deep combined Feynman + State Inconsistency audit orchestrated across 8 specialized agents, with dynamic domain pattern discovery.

Activation

  • User says /nemesis-scan or nemesis scan or deep combined audit
  • User wants maximum-depth business logic + state inconsistency coverage

Invocation Format

/nemesis-scan [target] [optional: --hints "domain description"] [optional: --fresh]

Examples:

  • /nemesis-scan src/contracts/ — audit contracts, auto-discover domain
  • /nemesis-scan src/consensus/ --hints "DAG-based BFT consensus" — audit with domain hints
  • /nemesis-scan src/ --fresh — force domain pattern regeneration

Execution

  1. Determine the target scope from the user's request (files, directories, or modules to audit)
  1. Parse optional arguments:
  • Domain hints: Extract text after --hints (quoted string). If absent, set to "none".
  • Fresh flag: If --fresh is present, skip cache check and force domain discovery.
  1. Create the output directory:

``bash mkdir -p .audit/nemesis-scan/research .audit/findings ``

  1. Cache check — determine if domain discovery is needed:

``bash # Check if cached domain-patterns exist if [ -f .audit/domain-patterns.md ]; then head -5 .audit/domain-patterns.md fi ``

Read the header of .audit/domain-patterns.md if it exists. The cache is valid when ALL of:

  • The file exists
  • The _Git hash:_ line matches current git rev-parse --short HEAD
  • The _Target scope:_ line matches the requested scope
  • The _User hints:_ line matches the provided hints
  • The --fresh flag was NOT passed

Set discovery_needed = true if cache is invalid or missing. Set discovery_needed = false if cache is valid.

  1. Resolve the path to this skill's references/ directory for agent prompts.
  1. Spawn the nemesis-orchestrator agent:
Agent({
  subagent_type: "nemesis-orchestrator",
  description: "Run nemesis-scan pipeline",
  prompt: "Run the full nemesis-scan pipeline on the following target scope:

Target: [target files/directories]
Domain hints: [user hints or 'none']
Discovery needed: [true/false]

References are at: [absolute path to skills/tn-nemesis-scan/references/]

All agents MUST read core-rules.md and language-adaptation.md.

[If discovery_needed is true:]
Run Phase -1 (Domain Discovery) FIRST:
- Phase -1a: Spawn nemesis-strategy with target scope, hints, and research-guide.md
- Phase -1b: Spawn parallel nemesis-researcher agents (one per research topic from strategy plan)
- Phase -1c: Compile fragments into .audit/domain-patterns.md with cache metadata

[If discovery_needed is false:]
Skip Phase -1. Domain patterns are cached at .audit/domain-patterns.md

Then execute all 8 phases in order, with all agents reading .audit/domain-patterns.md for domain context:
- Phase 0+1 (parallel): nemesis-recon + nemesis-mapper
- Phase 2: nemesis-feynman (full mode)
- Phase 3: nemesis-state-check (full mode)
- Phase 4: feedback loop (max 3 iterations)
- Phase 5: nemesis-journey
- Phase 6: nemesis-verifier
- Phase 7: nemesis-reporter

Additionally, load bundled domain references based on the target scope:
- If target includes epoch boundaries, system calls, validator lifecycle, ConsensusRegistry, StakeManager, region, shuffle, geographic, diversity, slash, applySlashes, burn, confiscate, committee size, or setNextCommitteeSize → also read references/protocol-contract-patterns.md
- If target includes consensus state, DAG, certificates, aggregators, state sync, network/peer management, batch, builder, pool, transaction ordering, subscriber, finality, CVV, NVV, observer, storage, persistence, archive, recovery, peer score, Kademlia, or reputation → also read references/consensus-dag-patterns.md

Write phase outputs to .audit/nemesis-scan/
Write final reports to .audit/findings/nemesis-scan-verified.md and .audit/findings/nemesis-scan-raw.md

Present a concise summary when complete."
})
  1. After the orchestrator returns, relay its summary to the user with paths to the report files.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.