This page holds no documented attribute, no price and no cited stack edges; anything the vendor added is marked and does not count. So it is excluded from search engines until it holds something. Thin pages get penalised at scale, and a page that says nothing should not be indexed as though it did.
A link to a public page that states what it is, costs or runs on is what fills it. Send one. From agent-threat-rules? Claiming also lets you write the tagline, description, logo, docs link and deployment model (what a claim covers).
agent-threat-rules
UNCLAIMEDMODEL SECURITY AND SUPPLY CHAIN
agent-threat-rules — Open detection-rule standard for AI agent security threats — like Sigma, but for AI agents. Executable rules across 10 categories; merged into Microsoft AGT, Cisco AI Defense, MISP, OWASP, FINOS & Sig. Listed under Model security and supply chain in the Security / Governance layer.
The open detection standard for AI agent security. 836 rules. 101,280 agent skills scanned in the wild. MIT Licensed.
4 OF 4 SIGNALS HELD
What it runs on, and what runs on it
0 cited edgesComputed from the stack graph, both directions. Every cited edge links the page it was read from; a vendor-added one links the vendor’s own source — this is the reason to be here rather than on the vendor’s own site.
No edges on record for agent-threat-rules.
Nothing in the directory documents depending on it, and its own docs do not name what it runs on. An edge is only stored when a source states it.
Submit a documented integration →From agent-threat-rules? No claim is needed for this: a link to your docs that names what agent-threat-rules runs on is enough.
Open-source signals
A HOLLOW RING IS UNMEASURED, NOT ZERO · WE DO NOT SUBSTITUTE A PARENT COMPANY’S REPOSITORY FOR A PRODUCT THAT HAS NONE
Price
We hold no price for this product.
This is open-source software: you can run it yourself and the licence costs nothing. If the project also sells a hosted service, we do not yet hold the page it prices it on. If that changes — or if you publish /.well-known/pricing.json — it appears here with a capture date.
How we read prices →What its categories ask
No questions are declared yet for Model security and supply chain.
A category earns its questions from what buyers actually compare, and this one has not been given any. Until it is, this listing is compared on price, open-source signals and its stack edges alone — not because nothing was answered, but because nothing was asked.
How the taxonomy is built →Practitioner reviews
Nobody has written one yet.
A review here is structured, not a star: hardware, scale band, what broke in production, and whether you would choose it again.
NO PERCENTAGE IS SHOWN UNDER FIVE REVIEWS · NO STAR RATINGS, EVER
Also in this category
3 products in Model security and supply chain. Comparison defaults to within the category — pairing this with a GPU cloud would produce a page that means nothing.
USED BY = LISTED PRODUCTS DEPENDING ON IT, IN THIS DIRECTORY
Frequently asked
Is agent-threat-rules open source?
What does a blank mean on the agent-threat-rules page?
Where do the agent-threat-rules figures come from?
Can agent-threat-rules change what this page says?
Something here is wrong — how do I fix it?
Is this listing run by agent-threat-rules?
Cite this page
A model that quotes us should quote us correctly. The reading and its date sit inside the citation rather than beside it, because a quotation carrying only a URL goes wrong the week the URL changes.
infratoapp, “agent-threat-rules — Model security and supply chain”. https://www.infratoapp.com/products/agent-threat-rules
What agent-threat-rules can and cannot change here
Claiming the organisation lets its admins and editors change the tagline, description, logo, docs link and deployment model of every product that org owns — live, labelled as theirs, and logged. Answers to blank questions and dependencies go live too, marked as the owner’s and sourced; a documented answer cannot be overwritten. Everything else on this page is a stated fact with a dispute route: price, licence and OSS figures. Those columns are ungranted at the database level, so they are not a feature we withheld — they are a write that cannot happen. Name, category, website, pricing page and package names can be changed by the owner only through our review. A dispute never deletes a value; it marks it and publishes the correction.