**New Active Fork + Proposal for Ongoing Maintenance**

.github/CODE_OF_CONDUCT.md

@@ -1,46 +1,5 @@
-# Contributor Covenant Code of Conduct
+# Contributor Code of Conduct
 
-## Our Pledge
+_be excellent to each other_
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at trimstray@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+thank you for coming to my Ted talk

.github/ISSUE_TEMPLATE/broken-link-or-update.yml

@@ -0,0 +1,42 @@
+name: Broken Link or Outdated Resource
+description: Report a dead link, moved resource, or something that needs updating
+title: "[Fix] Broken/Outdated: Brief description"
+labels: ["maintenance", "bug"]
+body:
+  - type: input
+    id: url
+    attributes:
+      label: Problematic URL
+    validations:
+      required: true
+
+  - type: input
+    id: location
+    attributes:
+      label: Where is this link located?
+      placeholder: e.g., README.md line 456, or ./hacking-pentesting/wordlists.md
+
+  - type: dropdown
+    id: issue_type
+    attributes:
+      label: Type of Issue
+      options:
+        - 404 / Not Found
+        - 403 / Forbidden
+        - Redirected / Moved
+        - Outdated / Deprecated
+        - Better Alternative Exists
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: suggestion
+    attributes:
+      label: Suggested Fix / Replacement
+      placeholder: "Replace with https://new-working-url.com (status 200); or remove if obsolete."
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false  # Disable "Open a blank issue" to encourage template use
+contact_links:
+  - name: General Questions or Discussions
+    url: https://github.com/jacob-kraniak/the-book-of-secret-knowledge/discussions
+    about: For questions, ideas, or open discussion — please use Discussions instead of issues.
+  - name: Contact Maintainer (Jacob)
+    url: https://x.com/JacobSk92
+    about: For private or urgent outreach.

.github/ISSUE_TEMPLATE/general-enhancement.yml

@@ -0,0 +1,20 @@
+name: General Enhancement or Idea
+description: Propose any other improvement (navigation, formatting, new feature like search, etc.)
+title: "[Enhancement] Short title"
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description of the Enhancement
+      value: |
+        **Is your feature request related to a problem? Please describe.**
+        A clear and concise description of what the problem is.
+
+        **Describe the solution you'd like**
+        A clear and concise description of what you want to happen.
+
+        **Additional context**
+        Add any other context or screenshots about the feature request here.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/question-or-discussion.md

@@ -0,0 +1,18 @@
+---
+name: Question or Open Discussion
+description: Have a question or want to discuss something? → Use Discussions instead!
+title: "[Discussion] "
+labels: ["question"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for wanting to start a conversation!
+
+        For questions, brainstorming, or non-actionable discussion, please use **GitHub Discussions** instead:
+
+        👉 https://github.com/jacob-kraniak/the-book-of-secret-knowledge/discussions/new
+
+        This helps keep Issues focused on actionable work (bugs, features, migrations).
+
+        You can close this issue now — or comment if you really prefer it here.

.github/ISSUE_TEMPLATE/resource-suggestions.yml

@@ -0,0 +1,76 @@
+name: Resource Suggestion
+description: Suggest adding or updating a tool, link, blog, cheat sheet, one-liner, etc.
+title: "[Resource] Short descriptive title"
+labels: ["resource", "enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for suggesting a resource! Please fill out as much as possible.
+
+  - type: input
+    id: name
+    attributes:
+      label: Resource Name
+      description: Name of the tool, blog, list, one-liner collection, etc.
+      placeholder: e.g., "nmap", "PayloadsAllTheThings", "Shell One-liner: Find large files"
+    validations:
+      required: true
+
+  - type: input
+    id: url
+    attributes:
+      label: URL / Location
+      description: Direct link (or file path if already in repo)
+      placeholder: https://example.com/tool or ./shell-utils/one-liners/find-large-files.md
+    validations:
+      required: true
+
+  - type: dropdown
+    id: category
+    attributes:
+      label: Which section/category does this belong to?
+      options:
+        - CLI Tools
+        - GUI Tools
+        - Web Tools
+        - Systems & Services
+        - Networks
+        - Containers & Orchestration
+        - Manuals / Howtos / Tutorials
+        - Inspiring Lists
+        - Blogs / Podcasts / Videos
+        - Hacking / Penetration Testing
+        - Daily Knowledge / News
+        - Cheat Sheets
+        - Shell One-liners / Tricks / Functions
+        - Other (please specify below)
+      default: 0
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description & Why Include It
+      description: Brief summary + why it's valuable / unique / up-to-date.
+      placeholder: "nmap is the de facto network scanner; still actively maintained in 2026."
+    validations:
+      required: true
+
+  - type: input
+    id: tags
+    attributes:
+      label: Suggested Tags / Keywords
+      description: Comma-separated (helps future search/tagging)
+      placeholder: nmap, scanning, network, cli
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Checklist
+      options:
+        - label: I have searched existing resources / issues to avoid duplicates
+          required: true
+        - label: The resource is legal, ethical, and publicly available
+          required: true

.github/ISSUE_TEMPLATE/section-migration.yml

@@ -0,0 +1,47 @@
+name: Section Migration / Restructure
+description: Propose or work on moving a README section to subfolder/files
+title: "[Migration] Move/Refactor: Section Name"
+labels: ["migration", "structural", "help wanted"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this for tracking the big structural refactor (moving content from README.md into dedicated folders/files).
+
+  - type: input
+    id: section
+    attributes:
+      label: Section / Subsection to Migrate
+      placeholder: e.g., CLI Tools → Network subsection, or Hacking/Penetration Testing → Labs & CTFs
+    validations:
+      required: true
+
+  - type: input
+    id: target
+    attributes:
+      label: Proposed Target Location
+      placeholder: e.g., /cli-tools/network.md or /hacking-pentesting/labs-ctfs.md
+    validations:
+      required: true
+
+  - type: textarea
+    id: notes
+    attributes:
+      label: Migration Notes / Decisions
+      description: Any consolidation, deduplication, renaming, or special handling needed?
+      placeholder: "Consolidate multiple CTF/lab mentions into one file; remove 404 links; add YAML frontmatter for tags."
+
+  - type: textarea
+    id: blockers
+    attributes:
+      label: Potential Blockers or Dependencies
+      placeholder: "Depends on folder skeleton being created first; needs review of overlapping sections."
+
+  - type: checkboxes
+    id: status
+    attributes:
+      label: Current Status (self-check)
+      options:
+        - label: This is a proposal (not yet started)
+        - label: In progress (link PR below if exists)
+        - label: Ready for review

.github/workflows/ai-pr-review

@@ -0,0 +1,110 @@
+name: Grok AI PR Review
+
+on:
+  pull_request:
+    types: [opened, synchronize, reopened]
+
+permissions:
+  pull-requests: write
+  contents: read
+
+jobs:
+  review:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # Needed for git diff
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install openai requests
+
+      - name: Run Grok Review
+        env:
+          XAI_API_KEY: ${{ secrets.XAI_API_KEY }}
+          GROK_MODEL: ${{ vars.GROK_MODEL || 'grok-code-fast-1' }}  # fallback to fast coding model
+        run: |
+          python - << 'EOF'
+          import os
+          import requests
+          from openai import OpenAI
+
+          # Use OpenAI SDK with custom base URL for xAI compatibility
+          client = OpenAI(
+              api_key=os.environ["XAI_API_KEY"],
+              base_url="https://api.x.ai/v1"
+          )
+
+          # Get PR diff via GitHub API (or git diff origin/${{ github.base_ref }}...HEAD)
+          repo = "${{ github.repository }}"
+          pr_number = ${{ github.event.pull_request.number }}
+          token = os.environ.get("GITHUB_TOKEN")  # built-in
+
+          headers = {
+              "Accept": "application/vnd.github.v3.diff",
+              "Authorization": f"token {token}"
+          }
+          diff_url = f"https://api.github.com/repos/{repo}/pulls/{pr_number}"
+          diff_response = requests.get(diff_url, headers=headers)
+          diff_text = diff_response.text
+
+          if not diff_text.strip():
+              print("No diff found or empty PR.")
+              exit(0)
+
+          # Truncate if too long (Grok context is large, but save tokens)
+          max_chars = 30000
+          if len(diff_text) > max_chars:
+              diff_text = diff_text[:max_chars] + "\n\n[Diff truncated; full context may be larger]"
+
+          # Strong, repo-specific prompt (tune this!)
+          prompt = f"""
+          You are a senior security & knowledge-base curator reviewing changes to 'The Book of Secret Knowledge' — a curated list of cybersecurity, pentesting, CLI/GUI tools, shell tricks, and secret-finding resources.
+
+          Review this PR diff carefully:
+          {diff_text}
+
+          Provide concise, actionable feedback in Markdown:
+          - **Summary**: One-sentence overview of changes
+          - **Strengths**: What is good (e.g., new valuable resources, clean formatting)
+          - **Issues/Suggestions**:
+            - Formatting/consistency (links, headings, lists)
+            - Potential inaccuracies or outdated info
+            - Security risks (e.g., dangerous commands without warnings)
+            - Improvements (clarity, better structure, missing cross-references)
+          - **Overall**: Approve, Request changes, or Comment (with emoji rating)
+
+          Be strict but constructive. Flag anything promotional/spammy.
+          """
+
+          response = client.chat.completions.create(
+              model=os.environ["GROK_MODEL"],
+              messages=[
+                  {"role": "system", "content": "You are an expert code/knowledge reviewer."},
+                  {"role": "user", "content": prompt}
+              ],
+              temperature=0.4,  # lower for focused reviews
+              max_tokens=1200
+          )
+
+          review_body = response.choices[0].message.content.strip()
+
+          # Post as comment
+          comment_url = f"https://api.github.com/repos/{repo}/issues/{pr_number}/comments"
+          comment_headers = {
+              "Accept": "application/vnd.github+json",
+              "Authorization": f"Bearer {token}",
+              "X-GitHub-Api-Version": "2022-11-28"
+          }
+          payload = {"body": f"### Grok AI Review\n\n{review_body}"}
+          requests.post(comment_url, json=payload, headers=comment_headers)
+          print("Review posted.")
+          EOF