4 articles
-
What is your agent allowed to fix on your server by itself?
An agent that patches your server by itself needs a mandate. This is how you decide which sources it trusts, what it is allowed to do on its own and what it leaves to you.
An agent that monitors and updates your server by itself sounds reassuring. Until you wonder what it is allowed to touch while you are asleep. In the previous article you read how Tom Verheyden forwarded me a warning about new security vulnerabilities. And how my Webmaster agent then built two skills and an automation in about twenty-five minutes, which run twice a day.
Here you can see how that works, so you can adopt the principle for what you have online yourself. I will leave out my own settings. Copy the starting prompt at the bottom of this article, and let your agent make an inventory of your own server first.
Free with an accountRead -
How to help build a stronger internet together
Did you put something online yourself after a workshop? After a week full of security leaks, you can read here how an agent guards your server for you, including the prompt.
Last night, Tom Verheyden forwarded me an email from his hosting provider. It warned about a series of security leaks that became known this week. It was about even more security risks related to PHP, about Node.js and about eMudhra, a certificate authority whose keys were stolen. Tom added one line himself:
'Hmmm... it does not exactly stop with just PHP.'
With a half-awake head, I read that this morning with my coffee. I was awake immediately, and that was not because of the coffee. My first thought went to you. Perhaps you put something online yourself after a workshop on Claude, AI Agents or Vibe Coding: a little tool, a small app, a website. Then this news is actually about you too.
Free with an accountRead -
Step-by-step plan, your first email agent in six steps
Six steps with ready-to-use prompts to build an agent that goes through your emails every morning and tells you what needs your attention today. Ready in half an hour.
I think an agent that goes through your emails every morning is the best first agent you can build. It is small. And you will use it the very next day. This step-by-step plan takes you from an empty chat to an agent you have tested yourself. I wrote it for Copilot, but the prompts also work in Claude or ChatGPT. Count on half an hour.
The first step, in a regular chat
I actually ignore the agent builder. I just start in a chat. And then I let my AI ask questions first. The vague parts in your assignment are exactly what it needs to figure out. Fill in the part in brackets.
Free with an accountRead -
Your first agent only sees your mailbox
An agent that checks your emails every morning is an ideal first agent. This is how you write the instruction and how you give it only what it needs.
I am very often on the road to give training myself. And then I do not read my emails, of course. And I am far from the only one in that, as it turned out during the last workshop on Copilot. During the introductions, everyone talks about their mailbox, which is always overflowing. One person literally said: 'I have already tried everything: rules, folders, categories, ... but I get hundreds of emails a day! It is simply impossible to keep up with!'
And then I demonstrated how you build an agent that checks your emails. And it does one thing: every morning at 06:00 it checks your emails from the previous day, and gives you a summary: what is a priority, what is spam, which actions you definitely need to do today.
Free with an accountRead