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

How to propose a new hazard placard category with AI Charter

Add a labeled, severity-rated hazard entry to the placard definitions and open a pull request.

Who it is forAn AI safety or risk researcher who has found a hazard type that the current placard list does not cover.

The problemA certification cannot disclose a hazard that has no placard category, and the list has no built-in way to add one.

The outcomeA pull request that adds a new hazard placard with a label, severity, and one-line description to the shared definitions.

What you need first

  • Node.js and npm to run the site locally
  • Git and a GitHub account to submit a pull request
  • Model details ready for the certify form: company, version, status, training sources, hazard categories, and unintended consequences

Steps

  1. Clone the repository with git and open the project folder. (inferred, check the README)
  2. Run npm install in the project folder.
  3. Open src/types/certification.ts and add an entry to HAZARD_CATEGORY_DEFINITIONS with a label, severity, and one-line description.
  4. Run npm run build to type-check the change.
  5. Open a pull request against src/types/certification.ts.

Prompt for your agent

In the mrtinkz/ai-charter repository, add a hazard entry to HAZARD_CATEGORY_DEFINITIONS in src/types/certification.ts for <hazard name>, with a label, severity, and one-line description. Run `npm run build`. Expected output: a passing build and a diff that adds only that entry. Verify the new entry appears on /placards after `npm run dev`.

Caveat. The README does not say how severity levels are defined, so the severity value a contributor picks needs to be justified in the pull request.

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