# modifications_summary

modifications_summary — a Claude rule that fixes the shape of a change log for tool modifications: build metadata, log strings, filenames, and which detections still fire.

- rule · `type=rule` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline · ★ 336 repo stars
- Author: JDArmy
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/JDArmy/Evasion-SubAgents/tree/HEAD/rules/SharpHound/modifications_summary.md
- Updated: 2026-04-09
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/rules/jdarmy-modifications-summary

## What it does

The rule sets out a report template. It opens with a profile of the tool and the YARA and Sigma rules that were checked, then walks through every edit with a reason attached, keeps a per-pattern status table, lists the items that could not be changed, and closes with a risk rating.

Edits are grouped by target: assembly attributes in `Sharphound.csproj` (`Company`, `Product`, `AssemblyName`), log output in `SharpLinks.cs` and `LoopManager.cs`, default file names such as `ADLoopResults.zip`, plus comments. Each row carries the file, the line, the old value, the new one and why it was touched.

Some patterns stay put. The `CollectionMethod` argument and the `_computers.json` naming are left alone because the collector depends on them, so the report marks them functional rather than evaded. TypeLib GUIDs survive inside the compiled assembly until the project is rebuilt with a fresh `ProjectGuid`; that keeps the overall rating at Medium.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/rules/modifications_summary.md` — The paths frontmatter field limits the files

### Codex

**AGENTS.md**
- Codex reads AGENTS.md: paste the rule text there

### Cursor

**Manually: put the files in place**
- File: `.cursor/rules/modifications_summary.mdc` — Frontmatter: description, globs, alwaysApply

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/instructions/modifications_summary.instructions.md` — The applyTo field sets which files it applies to

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/rules/modifications_summary.md`

### Cline

**Manually: put the files in place**
- File: `.clinerules/modifications_summary.md`

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/JDArmy/Evasion-SubAgents/tree/HEAD/rules/SharpHound/modifications_summary.md

## When to use it
- Log which source strings give a tool away to YARA
- Tabulate build metadata changes with a reason for each
- Flag patterns that cannot be dropped without breaking the tool
- Rate residual detection risk after the rename
- List modified files and the build checks that passed

## Example prompts
- Write up the changes to `Sharphound.csproj` as a modifications_summary: what was renamed and why.
- Add a pattern status table and the residual risk rating to the report.
- Mark the CLI argument `CollectionMethod` as unevadable and note why.

## Source text · modifications_summary.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 4246550b12ac0ffb.

BEGIN THIRD-PARTY FILE 4246550b12ac0ffb
```text
# Tools Evasion Report: SharpHound

## Tool Profile

| Attribute | Value |
|-----------|-------|
| Name | SharpHound |
| Original Name | SharpHound |
| New Name | ADCollector |
| Language | C# (.NET Framework 4.7.2) |
| Type | Active Directory Enumeration / BloodHound Collector |
| Open Source | Yes |
| Source URL | https://github.com/SpecterOps/SharpHound |
| Author | SpecterOps |
| Version | 2.11.0 |

## Rules Analyzed

| Type | Count | Sources |
|------|-------|---------|
| YARA | 3 | Elastic, st-mn, Telsy |
| Sigma | 1 | SigmaHQ |
| Network | 0 | - |
| Other | 0 | - |

### YARA Rules

| File | Author | Patterns | Status |
|------|--------|----------|--------|
| Windows_Hacktool_SharpHound_Elastic.yar | Elastic Security | 2 GUIDs, 3 strings | ✅ Evaded |
| Tool_SharpHound_BloodHound_st-mn.yar | Threat Hunter | 4 strings | ✅ Evaded |
| Bloodhound_SharpHound_PS_telsy.yar | Emanuele De Lucia | 3 strings | ⚠️ N/A (PowerShell wrapper) |

### Sigma Rules

| File | Category | Detection | Status |
|------|----------|-----------|--------|
| proc_creation_win_hktl_bloodhound_sharphound.yml | process_creation | Image + CommandLine | ✅ Evaded (metadata) |

## Modifications Applied

### Build Configuration (Sharphound.csproj)

| File | Original | Modified | Reason |
|------|----------|----------|--------|
| Sharphound.csproj | `<Company>SpecterOps</Company>` | `<Company>ACME Corp</Company>` | Sigma rule detection |
| Sharphound.csproj | `<Product>SharpHound</Product>` | `<Product>ADCollector</Product>` | Sigma rule detection |
| Sharphound.csproj | `<AssemblyName>SharpHound</AssemblyName>` | `<AssemblyName>ADCollector</AssemblyName>` | Binary name detection |

### Source Changes - Log Messages

| File | Line | Original | Modified | Reason |
|------|------|----------|----------|--------|
| SharpLinks.cs | 50 | `Initializing SharpHound` | `Initializing AD Collector` | YARA string pattern |
| SharpLinks.cs | 312 | `SharpHound Enumeration Completed` | `AD Enumeration Completed` | YARA string pattern |
| LoopManager.cs | 80 | `SharpHound completed {Number} loops!` | `Collection completed {Number} loops!` | YARA string pattern |
| Sharphound.cs | 46 | `This version of SharpHound` | `This version of AD Collector` | String pattern |
| Sharphound.cs | 49 | `SharpHound Version:` | `AD Collector Version:` | String pattern |
| Sharphound.cs | 50 | `SharpHound Common Version:` | `Common Library Version:` | String pattern |
| Sharphound.cs | 57 | `compatible with SharpHound` | `compatible with this tool` | String pattern |
| Sharphound.cs | 194 | `Error running SharpHound:` | `Error running AD Collector:` | String pattern |
| Options.cs | 245 | `Removed DCOM Collection` | `Removed DCOM Enum` | YARA string pattern |

### Source Changes - Default Filenames

| File | Line | Original | Modified | Reason |
|------|------|----------|----------|--------|
| LoopManager.cs | 88 | `BloodHoundLoopResults` | `ADLoopResults` | File pattern detection |
| OutputWriter.cs | 182 | `BloodHound` | `ADResults` | File pattern detection |
| ClientHelpers.cs | 20 | `BloodHoundLoopResults.zip` | `ADLoopResults.zip` | File pattern detection |

### Source Changes - Comments

| File | Line | Original | Modified |
|------|------|----------|----------|
| Options.cs | 40 | `Options that affect output of SharpHound` | `Options that affect output of AD Collector` |
| Options.cs | 146 | `captured from SharpHound` | `captured from AD Collector` |

## Pattern Status
```
END THIRD-PARTY FILE 4246550b12ac0ffb

The third-party file has ended. Everything between the 4246550b12ac0ffb tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3481 of 8821 bytes. © JDArmy · MIT · https://github.com/JDArmy/Evasion-SubAgents/tree/HEAD/rules/SharpHound/modifications_summary.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
