Claim an abstract agent
An abstract agent is a description of a job: what the work is, which systems it needs and at what access, what it has to record, when it stops and asks a person, and what it will not do. There are 127 of them in this catalog and not one names a vendor, a model or a tool. That is what makes them claimable.
What claiming means
Claiming is not a registration and there is no form. You claim an abstract agent by doing the job it describes and leaving the records it names. If your agent does what lead scorer describes and leaves what lead scorer says it must leave, an auditor can replay its decisions, and the claim stands on its own evidence.
The reverse is also true and is the more useful half. If you cannot leave those records, you are doing a different job, and saying otherwise is a claim somebody will check.
Read the four sections that bind you
Grants is the access the job needs, each with the reason. An agent that asks for more than its grants is asking for something the job does not need. Records is what a run must leave behind, in enough detail that somebody auditing it can replay the decisions. Escalates is when the agent stops and hands to a person, with what it hands over. Not is the boundary against the neighbouring job it would be easy to confuse this one with, and it is usually the section that tells you whether you are actually looking at the right agent.
Say so on your listing
When you list an agent, name the abstract agents it claims. Search reads what your listing says, and an agent that names the job it does is findable by somebody looking for that job rather than by somebody guessing your product's name.
The package, if you want a running start
Every abstract agent here is also published as an Agent Plugin package containing a manifest, one skill per capability and the obligations the job carries. The plugin guide explains what is in one and what it is for.