Community guidelines
Last updated: 1 November 2026
This translation is provided for convenience; the Spanish version prevails.
The thepat.io agent library works because people share with care. These guidelines say plainly what you can share, what you cannot, and what happens if something goes wrong.
In short. Share only what is yours or what you have permission to share, and make it genuinely useful. No tricking people, no pulling out anyone's data, no getting around permissions. What you share carries the CC-BY 4.0 licence and you can withdraw it whenever you like. Everything is reviewed before it is published, and you can report anything that looks wrong. Questions: support@thepat.io.
1. What the library is for
The library is a showcase of agents that anyone can add to their Pat office. It has two shelves: “From the house”, with the agents we make ourselves (Pat, Lúa, Milo, Nico, Vera and Bruno), and “Community”, with agents shared by other people or brought in from open projects.
- No agent comes preinstalled: it only joins your office if you add it, or if you ask Lúa or Pat to.
- Community agents are contributions from people. They can be badly made or not suit you: the page tells you who made it, which hands it uses and how it is rated.
- A library agent never gets more permissions than the ones you give it, and the important things (paying, sending, publishing, deleting, buying) still need your OK.
2. What you can share
You can share an agent you created yourself or that you have the right to share. What gets published is the agent and nothing else:
- Its name, description, look and instructions.
- The tools (“hands”) it uses, so whoever adds it knows what it can do.
- A few usage examples that you write on purpose for the page.
- Never your memory, your files, your conversations, your connected accounts or your keys. Before publishing you see an exact preview of what goes out, and only that goes out.
To share you must be a person invited to the beta, have an account at least 3 days old and share no more than 5 agents a day. These limits help prevent abuse and may change.
3. What is not allowed
None of this is accepted, however well written and even if it is “just a test”:
- Instructions to deceive, extract data or bypass permissions. No agents that try to convince another agent or a person to ignore their rules, hide what they are doing, extract private information, ask for passwords, or get around the permissions and the “yeses” each person gives.
- Impersonation. Do not pose as a real person, a company or a brand, or use their names, logos or voice to suggest the agent is theirs or approved by them.
- Illegal, hateful, harassing or adult content. Nothing that incites violence or discrimination, harasses or threatens, exploits minors, is pornographic or sexually explicit, or helps commit a crime.
- Spam and hidden advertising. An agent cannot exist to sell something without saying so, flood people with messages, or steer someone to a product or website without making that clear.
- Copying without a licence. Do not upload other people's work without permission or without respecting its licence. If you drew on an open project, say which one.
- Other people's personal data. No names, phone numbers, emails, addresses or documents of people who have not given permission, and no agents built to gather that data.
- Medical, legal or financial advice presented as professional. An agent can explain and guide, but it cannot claim to be a doctor, a lawyer or an adviser, promise results, or push people into serious decisions without saying that a professional should be consulted.
4. The licence on what you share
When you share an agent, you publish it under the Creative Commons Attribution 4.0 licence (CC-BY 4.0). In plain words:
- Anyone can use, copy, adapt and improve your agent, even in a paid project, as long as they credit you as the author.
- The credit carries your name or the alias you choose when sharing. You do not have to use your real name.
- You remain the author: the licence does not take authorship away, it only lets other people use the work on those terms.
- You can withdraw your agent from the library whenever you like. It stops being shown and can no longer be added, but the copies other people already have in their office stay with them, because the licence was already granted to them.
- You can only share what is yours or what you have the right to license this way. If it is not yours, do not share it.
- If you delete your account, what you shared stays in the library as “Anonymous” (the link to your account and your alias is removed) or, if you prefer when deleting it, is withdrawn. By default it becomes anonymous.
5. How it is reviewed
Nothing reaches the library without a review, and the review happens in two stages:
- Automatic review in three layers. First, rules look for forbidden patterns (for example, instructions to bypass permissions or extract data). Then an AI model reads the agent and flags anything doubtful. Finally, the agent is tried out in an isolated office, with no access to anything of yours, to see what it really tries to do.
- A person, before publishing. During the beta, a person on our team also looks at every agent before it is published. If something is unclear, you are asked to change it or it is rejected with a reason.
- The “Certified by thepat.io” seal. An agent carries it once it has passed all of the above and someone on the team has reviewed it in depth. The seal is tied to one specific version: if the author publishes a new version, that version is reviewed again and does not inherit the seal.
- The seal is not a guarantee: it reduces risk but does not remove it. Community agents are still third-party content and you decide whether to add them.
- Community instructions are always treated as untrusted data: even if an agent says it can do something, it can only do what your permissions allow.
6. Versions and updates
- If an author improves their agent, it comes out as a new version and goes through review again.
- Whoever already has the agent decides whether to update. A new version never changes by itself what you already have in your office.
- The notes on each change help you see what is being modified before you accept.
7. Reports
If you see an agent that breaks these guidelines, you can report it from its page, with a reason and, if you like, a note.
- Each person can report an agent once.
- When an agent collects 3 reports from different people, it is hidden from the library while we look at it.
- A person on our team reviews it and decides: it is shown again, a change is requested, or it is withdrawn.
- Do not report out of disagreement or revenge. Repeated bad-faith reports can lead to sanctions.
- You can also write to us at support@thepat.io, especially if it involves your own personal data or content that impersonates you.
8. Sanctions and how to appeal
We try to be proportionate: normally a warning comes before a removal, and a removal before a block.
- Warning. When the problem is small or unclear, we tell you and give you the chance to fix it.
- Removal. An agent that breaks the guidelines is hidden or withdrawn from the library. Copies already in other offices cannot be recalled, but we stop offering it and, if there is a serious risk, we may warn whoever has it.
- Block. If someone keeps breaking the rules or does something serious (deliberate deception, impersonation, publishing illegal content), we may block their ability to share in the library and, in the most serious cases, suspend the account under the terms and conditions.
- How to appeal. If you think we got it wrong, write to support@thepat.io with the name of the agent and why you think it follows the guidelines. A person will look at it and reply with the reason for the decision, whatever it is.
9. Agents imported from open projects
Part of the library comes from open-source projects whose licences allow reuse. We treat them with the same respect as any author.
- Each page states who the original author is, which repository it comes from and under which licence (for example, “Based on X (MIT)”).
- We only accept projects under licences that allow this reuse and require the credit to be kept (MIT, Apache-2.0, BSD, ISC, CC0 or CC-BY). If a licence does not allow it, it is not imported.
- The instructions are kept as their author wrote them. We only translate the name and description on the page into Spanish, and we say so.
- If you are the author of a project and want the credit corrected or your work removed, write to support@thepat.io and we will take care of it.
These guidelines may change as the library grows. We will announce important changes. For any question, support@thepat.io. See also the Terms and conditions (section 17, on Pat's Office) and the Privacy policy.