DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to track authorized security findings to a verified disposition with J Space Cognition Suite

Record candidate, confirmed, rejected, and fixed security items with reproduction evidence.

Authorization notice. J Space Cognition Suite is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. Use only targets you are authorized to test, and keep any reproduction data or secrets out of the shared evidence files.

Who it is forA security reviewer doing authorized analysis of a project they are permitted to test, who needs to track each finding.

The problemSecurity candidates are often lost or closed without reproduction, which leaves findings unverified.

The outcomeA set of findings, each with a disposition backed by reproduction and controls, checked before shipment.

What you need first

  • A host that can load a local SKILL.md and retrieve its supporting files
  • Python 3.10 or later, using the python, python3, or py -3 command for your system
  • A copy of the complete j-space/ directory placed in the host's Skills directory
  • Access to the target project as a task directory, and permission for the host to run local commands
  • For xhigh work, a host that can actually launch child agents

Steps

  1. Initialize a high task for the authorized target with /scripts/control.py init --goal "Security review of <scope>" --next "Inspect entry points" --level high --module modules/repository.md. (inferred, check the README)
  2. Record each suspected issue as a candidate in the task state, then reproduce it with the target's own tests or a controlled check.
  3. Mark each candidate as confirmed, rejected, or fixed only after its reproduction and controls are recorded.
  4. Write evidence files for each disposition and submit them with /scripts/control.py report --agent root --round 1 --summary "Security disposition summary" --evidence <evidence file> --source <file> --next "Resolve open candidates". (inferred, check the README)
  5. Resolve all open candidates and run /scripts/control.py check --stage ship before delivering the review.

Prompt for your agent

Use the j-space skill at high level for the authorized security review of <target repo>. Track each candidate, confirm or reject it with a reproducible check, and record evidence for each disposition. Verify that no candidate remains open before running the ship gate.

Caveat. The README describes security tracking as evidence capture only, so reproduction and the security judgment remain the reviewer's responsibility.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page