DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to get a delivery report of what was checked and what was not with Sure Forge

Receive agent-written work with a clear list of verified, reused, and unchecked items.

Who it is forA person receiving work from an AI agent who needs to know what was actually tested before accepting it.

The problemAgents sometimes check a sample and call the work complete, which leaves gaps the receiver cannot see.

The outcomeA delivery report that lists what was verified, what was reused, and what was not checked, with any blocked checks named.

What you need first

  • An agent host that reads Agent Skill folders, such as Claude Code, Codex, Cursor, Devin CLI, or Hermes Agent
  • Node.js 22.20 or newer for the Skills CLI, or a manual copy of the skills/sureforge/ folder
  • Python 3.11 or newer for the verification scripts

Steps

  1. Run npx skills add Da7-Tech/SureForge from your project.
  2. Ask your agent to finish the work with the deliver phase and to report what was verified, what was reused, and what was not checked.
  3. Check that any check the agent could not run, such as a visual render, is reported as blocked and not claimed as done.
  4. Review the evidence record and coverage ledger before accepting the work.
  5. Send back any item marked unresolved or not checked for another round.

Prompt for your agent

Using the Da7-Tech/SureForge skill, freeze the candidate for <deliverable path>, inspect every agreed unit on that exact version, and report what was verified, what was reused, and what was not checked. Expected output: a delivery gate result and a coverage ledger. Verify that every item in the report is backed by evidence or marked as not checked.

Caveat. The README says the coverage ledger and evidence record come from the skill's templates, so their completeness depends on the agent following the text.

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